# Environment Variables Environment variables are named string values made available to processes and applications, commonly inherited by child processes and used to affect program behavior. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Native Marketplace integrations now support custom environments DevFeed: [Native Marketplace integrations now support custom environments]() Original publisher: [Read original article]() Author: Tony Pan Published: 2026-09-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment](), [Environment Variables](), [Command-line interface](), [REST API]() Tags: [cli](), [deployment](), [environment-variables](), [environments](), [rest-api](), [vercel]() ### AI overview Vercel now lets users connect native Marketplace resources to custom environments through the dashboard, CLI, or REST API. The resulting environment variables can be scoped to the selected environments, while existing deployments remain unchanged. ### Source excerpt You can now connect native Marketplace resources to custom environments. Previously, resource connections could only target production, preview, and development environments. Choose custom environments when connecting a resource from the Vercel dashboard, Vercel CLI, or REST API. Vercel scopes the environment variables created by the connection to the selected environments. For example, from the CLI: Existing deployments do not change. Create a new deployment after connecting a resource or changing its environment scope. Custom environments are available on Pro and Enterprise plans. Read the docs for connecting from the dashboard, the CLI --environment flag, and the REST API envVarEnvironments field. Read more ## Mem0 joins the Vercel Marketplace DevFeed: [Mem0 joins the Vercel Marketplace]() Original publisher: [Read original article]() Author: Tony Pan Published: 2026-09-16T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Artificial Intelligence](), [App](), [context](), [API keys](), [Command-line interface](), [Environment Variables]() Tags: [ai](), [ai-agents](), [app](), [billing](), [cli](), [context](), [environment-variables](), [free](), [giving](), [install](), [integration](), [vercel](), [volume]() ### AI overview Mem0 is now a native integration on the Vercel Marketplace, providing long-term memory for AI agents and apps across sessions. The integration includes billing through Vercel, automatic provisioning of a scoped Mem0 project and API key, and environment-variable configuration. Mem0 offers a free plan with usage limits and a $20-per-month plan for higher volume. ### Source excerpt Mem0 is now available as a native integration on the Vercel Marketplace, giving your AI agents and apps long-term memory. Mem0 remembers user preferences, facts, and context across sessions, so your app stops starting from scratch. Install from the Marketplace with integrated billing on your Vercel invoice, no separate account or key management. A scoped Mem0 project and API key are provisioned automatically and added to your project as environment variables, including MEM0_API_KEY. Mem0 offers a free plan with usage limits and a $20 per month plan for higher volume. To see it end to end, deploy the eve Memory Agent template, an eve agent with long-term memory powered by Mem0. Get started with Mem0 on the Vercel Marketplace or through the Vercel CLI, available to customers on all plans. Read more ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory]() Original publisher: [Read original article]() Author: Amanda Lange Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Large Language Model](), [.NET](), [ASP.NET](), [C#](), [Artificial Intelligence](), [Command-line interface](), [OpenAI](), [Environment Variables]() Tags: [account](), [agent](), [ai](), [api](), [c-sharp](), [cli](), [code](), [conversation-memory](), [developer-insights](), [environment-variables](), [how-to](), [llm](), [net](), [net-9](), [openai]() ### AI overview This tutorial shows how to build a C# .NET 9 ASP.NET Core service that preserves caller context, preferences, and action history across separate inbound calls using Twilio Conversation Memory and an LLM. ### Source excerpt How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory ## Using coding agents on a migration: Three practices that mattered DevFeed: [Using coding agents on a migration: Three practices that mattered]() Original publisher: [Read original article]() Author: Chandler Ortman Published: 2026-09-02T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [migration](), [clickhouse](), [AI-assisted coding](), [coding](), [configuration](), [Deployment](), [Environment Variables]() Tags: [cleanup](), [clickhouse](), [coding-agents](), [deployment](), [environment-variables](), [migration](), [prompt](), [pull-requests](), [temporal-voices]() ### AI overview The article examines coding agents used during a migration of Temporal Cloud usage and billing data to ClickHouse. It finds that the agents were most useful for cleanup and removal work, with durable cleanup instructions and exhaustive searches helping make that work practical. ### Source excerpt Three lessons from using coding agents during a ClickHouse migration, from cleanup automation to writing durable instructions that stay useful over time. ## OpenTelemetry Spring Boot Starter Adds Declarative YAML Configuration in Version 2.26.0 DevFeed: [OpenTelemetry Spring Boot Starter Adds Declarative YAML Configuration in Version 2.26.0]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-14T07:47:36Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [Spring Boot](), [YAML](), [configuration](), [Environment Variables](), [telemetry](), [tracing]() Tags: [configuration](), [environment](), [java](), [opentelemetry](), [schema](), [setup](), [spring-boot](), [telemetry](), [traces](), [yaml]() ### AI overview The article explains how declarative configuration in the OpenTelemetry Spring Boot starter, available from version 2.26.0, embeds the SDK's YAML schema in application.yaml. It contrasts this approach with environment-variable configuration and describes how the YAML schema can represent telemetry pipelines and options beyond the fixed environment-variable catalog. ### Source excerpt The OpenTelemetry Spring Boot starter gained declarative-configuration support starting in version 2.26.0 -- the same YAML schema the Java agent introduced in late 2025, now embedded inside application.yaml. This post traces what one env var, OTEL_SERVICE_NAME=petclinic, does in that new world, and where the seams are. In a hurry? Jump straight to the Spring Boot starter declarative-config docs, paste your application.properties into the interactive converter, or pick your SDK setup in the Ecosystem Explorer with the Spring Boot starter target selected. Come back for the story when you have a coffee. ## Tetragon 1.7 adds fentry sensing, environment variable capture, parent-process visibility, and scoped policies DevFeed: [Tetragon 1.7 adds fentry sensing, environment variable capture, parent-process visibility, and scoped policies]() Original publisher: [Read original article]() Author: Paul Arah Published: 2026-06-09T14:01:46Z Content type: release Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [Processes](), [Environment Variables](), [context]() Tags: [cilium](), [ebpf](), [environment-variables](), [hubble](), [isovalent](), [kubernetes-networking](), [load-balancer](), [mesh-networking](), [policy](), [process](), [runtime-security](), [sensor](), [tetragon](), [visibility](), [website]() ### AI overview Tetragon 1.7 introduces a new fentry sensor, environment variable capture, parent-process visibility, and granular policy scoping with hostSelector. ### Source excerpt Tetragon 1.7 introduces a new fentry sensor, environment variables capturing, parent process visibility, granular policy scoping with hostSelector and more! ## Using Authentication Credentials within NetBox Webhooks DevFeed: [Using Authentication Credentials within NetBox Webhooks]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-05-19T10:30:32Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [NetBox](), [Authentication](), [Environment Variables](), [configuration]() Tags: [authentication](), [blog](), [ci-cd](), [configuration](), [credentials](), [docker](), [environment-variables](), [kubernetes](), [netbox](), [webhooks]() ### AI overview This tutorial explains how to provide authentication credentials in NetBox webhooks without hardcoding secrets in webhook configuration. It presents a custom Jinja2 filter that exposes selected environment variables to webhook headers or bodies, with examples for self-hosted and container-based NetBox deployments. ### Source excerpt Background A question that came up during a recent NetBox training session was: "How should authentication credentials be provided within NetBox webhooks?" For example, you may need to send a webhook from NetBox to an external system such as: CI/CD platforms internal APIs configuration management systems notification ## Public Environment Variables For Your Tests Using cypress-expose Plugin DevFeed: [Public Environment Variables For Your Tests Using cypress-expose Plugin]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-03-12T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Environment Variables](), [Processes]() Tags: [ci](), [configuration](), [cypress](), [environment](), [environment-variables](), [password](), [plugin](), [products](), [secrets](), [testing](), [tests]() ### AI overview This tutorial explains how the cypress-expose plugin passes public process environment variables into Cypress tests after Cypress v16 made such variables private by default. It warns that the plugin is intended only for non-secret data. ### Source excerpt Recently Cypress announced a change in how it will handle environment variables. Variables were always public and accessible to the appli ## Migrating From Cypress.env To cy.env and Cypress.expose Methods DevFeed: [Migrating From Cypress.env To cy.env and Cypress.expose Methods]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-03-07T05:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Environment Variables](), [Testing](), [Node.js](), [Playwright]() Tags: [cypress](), [environment-variables](), [playwright](), [products](), [secrets](), [testing]() ### AI overview A Cypress migration tutorial explains changes to environment values and secrets planned for Cypress v16. It describes how Cypress v15 exposes values to browser-run tests and recommends keeping secrets needed only by Node.js tasks out of the browser. ### Source excerpt Cypress v15.10.0 has announced a big switch coming in v16 - the new way of dealing ## Validate Environment Variables with Pydantic DevFeed: [Validate Environment Variables with Pydantic]() Original publisher: [Read original article]() Author: Rick Donato Published: 2025-12-02T08:00:19Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [Pydantic](), [Environment Variables](), [.env](), [Python]() Tags: [env-file-security](), [environment-variables](), [python](), [settings](), [tips]() ### AI overview A brief tutorial tip showing how to validate environment variables from .env files with Pydantic before they reach an application. It also notes that this can remove the need to manually call python-dotenv. ### Source excerpt Tip! Validate your env vars from your .env files before they hit your application by using Pydantic. This also eliminates the need to call python-dotenv manually. Here's an example: # uv add pydantic pydantic-settings python-dotenv from pydantic import Field, AnyHttpUrl, ValidationError from pydantic_settings import BaseSettings, ## How the Fury ecosystem manages high-frequency deployments with automation, monitoring, and resilience DevFeed: [How the Fury ecosystem manages high-frequency deployments with automation, monitoring, and resilience]() Original publisher: [Read original article]() Author: Juan José Orjuela Published: 2025-10-21T13:12:29Z Content type: tutorial Language: en Sources: [Mercado Libre Tech]() Topics: [Deployment](), [Deployment Strategies](), [Automation](), [Resilience](), [configuration](), [Environment Variables]() Tags: [architecture](), [automation](), [configuration](), [continuous-deployment](), [deployment](), [deployment-strategies](), [devops](), [environment-variables](), [metrics](), [on-call](), [optimization](), [resilience](), [scalability](), [vulnerabilities]() ### AI overview This article explains how the Fury ecosystem defines and manages deployments at high frequency. It covers deployment strategies, configuration changes, automatic redeployments, testing, monitoring, alerts, metrics, and on-call practices intended to maintain operational stability. ### Source excerpt "How do you manage to perform 30.000 deployments a day and still operate normally?" For many, that number sounds simply unattainable. Deploying thousands of times a day suggests chaos, constant risk, and an operation that's hard to sustain. But the reality is different: not only do we make it possible -- we do it with control, resilience, and full visibility. It's not magic or luck. It's about a deployment ecosystem built to scale, with robust processes, smart automation, and practices that let us maintain stability even with frequent changes. +750K deployments in July 2025, broken down by deployment strategy. In this article, we'll explain how our model works: what we consider a deployment, how our system is structured, what tools we use to monitor operational health, and how we respond to alerts and failures -- whether they happen in test environments or in the most critical areas of the business. Yes, we'll also cover alerts, metrics, and on-call rotations -- and why they're essential to maintaining a continuous and reliable deployment model at this scale. General outline of a deployment in the Fury ecosystem.What do we consider a deployment? In Fury, a deployment isn't just about pushing new code. We consider a deployment to be any action that updates the state of an application in a given environment. For example: Deploying a new code change to the platform using any of our supported strategies, such as Blue-Green, Canary-Safe, Rolling Update, or All-In. Updating environment variables or configuration properties: any change to these parameters requires a deployment, as it involves recreating the application with the new active configuration. Automatic re-deployments: these can be triggered not only due to detected vulnerabilities but also due to optimization opportunities that help reduce computing resource usage and operational costs. Running validations or tests in test environments before promoting changes to production. Supported deployment strategies Our plat ## Migrating Your Content Management System (CMS) Assets With MongoDB and Node.js DevFeed: [Migrating Your Content Management System (CMS) Assets With MongoDB and Node.js]() Original publisher: [Read original article]() Author: Nic Raboy Published: 2025-05-09T12:00:00Z Content type: tutorial Language: en Sources: [Nic Raboy]() Topics: [Content Management System](), [MongoDB](), [Node.js](), [migration](), [Development](), [axios](), [Environment Variables]() Tags: [axios](), [cms](), [developer](), [environment-variables](), [javascript](), [migration](), [mongodb](), [node-js](), [nosql](), [tutorial]() ### AI overview A tutorial explaining how to migrate content from a MongoDB-based content management system to external publishing platforms. It covers exporting written content and downloading media assets from third-party servers using Node.js, MongoDB, Axios, and environment variables. ### Source excerpt Content platforms evolve as business strategies shift. At MongoDB, we embraced external publishing platforms like Dev.to, Medium, The Polyglot Developer, etc. to better engage developer communities, r... The post Migrating Your Content Management System (CMS) Assets With MongoDB and Node.js appeared first on DEV. ## Using the 1Password CLI to Manage .env Configuration DevFeed: [Using the 1Password CLI to Manage .env Configuration]() Original publisher: [Read original article]() Author: Mattt (mattt@nshipster.com) Published: 2025-01-01T08:00:00Z Content type: tutorial Language: en Sources: [NSHipster]() Topics: [.env](), [Command-line interface](), [Environment Variables](), [Development](), [passwords]() Tags: [cli](), [configuration](), [development](), [environment-variables](), [miscellaneous](), [passwords]() ### AI overview This article explains how .env files can create onboarding, multi-environment, and change-tracking problems in development workflows. It introduces the 1Password CLI, or op, as a command-line tool for managing secrets and configuration. ### Source excerpt .env files can create friction in development workflows -- especially as teams and projects grow over time. If you're feeling this pain, the 1Password CLI (op) might be just what you need. ## Heroku AI | Managed Inference and Agents DevFeed: [Heroku AI | Managed Inference and Agents]() Original publisher: [Read original article]() Author: Rand Arete Published: 2024-12-02T14:00:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [AI Infrastructure](), [AI Models](), [Command-line interface](), [Large Language Model](), [Retrieval-Augmented Generation](), [Environment Variables]() Tags: [ai](), [ai-infrastructure](), [ai-models](), [cli](), [environment-variables](), [heroku-ai](), [large-language-models-llms](), [managed-inference-and-agents](), [news](), [nextgen](), [rag]() ### AI overview Heroku announces the pilot of Managed Inference and Agents, the initial offering of Heroku AI. It provides access to selected AI models and supports adding model access to Heroku applications through the Heroku CLI and environment variables. ### Source excerpt Over the last couple of years, we've repeatedly heard the question "who will build the Heroku of AI?". The answer to that question is that Heroku will, of course. We are excited to bring AI to the Heroku platform with the pilot of Managed Inference and Agents, delivered with the graceful developer and operational experience [...] The post Heroku AI | Managed Inference and Agents appeared first on Heroku. ## Blog: Introducing Falco 0.37.0 DevFeed: [Blog: Introducing Falco 0.37.0]() Original publisher: [Read original article]() Published: 2024-01-30T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Kubernetes](), [Scalability](), [Kernel](), [eBPF](), [x86](), [Environment Variables](), [Maintainers]() Tags: [ebpf](), [environment-variables](), [falco](), [kernel](), [kubernetes](), [maintainers](), [release](), [scalability](), [ux-improvements](), [version](), [x86]() ### AI overview Falco 0.37.0 is released with changes to Kubernetes metadata enrichment, kernel driver downloading and building, syscall emulation on x86_64, rule overrides, engine configuration, and environment-variable expansion. The release also includes breaking changes and UX improvements. ### Source excerpt Dear Falco Community, today we are happy to announce the release of Falco 0.37.0! This release brings an improved installation experience, a new way to modify Falco rules, and some great UX improvements. There are, as to be expected, a handful of breaking changes. But, rest assured, we've done all we can to help you with any changes you might need to make. During this release cycle, we merged more than 100 PRs on Falco and more than 160 PRs for libs and drivers, version 0.14.2 and version 7.0.0 respectively. Thank you to our maintainers and contributors, as this would not happen without your support and dedication! To learn all about these changes, read on! What's new? TL;DR Key features: A new way to enrich syscalls with Kubernetes metadata, replacing the old Kubernetes collector. New capabilities in falcoctl to download and build our kernel drivers, replacing the old falco-driver-loader script. Support for 32-bit syscall emulation on x86_64 in all kernel drivers (modern_ebpf, ebpf, kernel module). A new override key to easily modify rules, lists, and macros. Key UX improvements: Introduction of a new engine key in falco.yaml to replace all other methods for opening engines such as FALCO_BPF_PROBE, --modern-bpf, -g, and -e. Expansion of environment variables in falco.yaml even when they are part of a string. This release also comes with breaking changes, we'd suggest to read them before upgrading. If you use helm, make sure to read the Helm chart breaking changes page as well. Major features and improvements The 0.37.0 release contains a number of feature and UX improvements, here are list of some of the key new capabilities. A new way to enrich syscalls with K8s metadata Falco 0.37.0 introduces a new method to enrich syscalls with Kubernetes metadata to help address scalability and other issues with the old collector. Falco always had Kubernetes support, but sometimes we need new approaches to keep up with the bigger and bigger scale that we see in production clus ## Running Multiple Rails Apps Concurrently with Foreman and Procfile.dev DevFeed: [Running Multiple Rails Apps Concurrently with Foreman and Procfile.dev]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-07-18T13:15:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Environment Variables](), [Development](), [Yarn](), [Processes](), [Unix]() Tags: [dev](), [environment-variables](), [foreman](), [node](), [port](), [process](), [procfile](), [rails](), [run](), [unix]() ### AI overview A tutorial on running multiple Rails applications concurrently with Foreman and Procfile.dev. It explains how port conflicts can come from Node running behind Yarn and recommends assigning Yarn a port so Node inherits it through the environment. ### Source excerpt Pizza courtesy of Pizza for Ukraine! Donate Now to Pizza for Ukraine As I've said, I build a lot of side projects and I really, really like the model of having: ALL MY APPS RUNNING CONCURRENTLY I may be a scattered, distracted developer trying to do too damn much but that's my damn right. And I have 64 gigs of RAM so why shouldn't I be this way. What I want is to be able to switch from app to app and make changes. This is important because some apps provide APIs which other apps rely on and having to figure out what thing is on what port, etc, is just plain distracting. Foreman and Procfile.dev is a way around this but there's a major hitch in your getalong (as my Texas wife might say). Here's a sample Procfile.dev for an app I'm building called Cartazzi which makes a developer's life easier: web: bin/rails server -p 5000 css: yarn build:css --watch js: yarn build --reload # docker: docker-compose up And here's a Profile.dev for another application called Poolwizard which helps you maintain your swimming pool: #web: bin/rails server -p $PORT web: bin/rails server -p 5700 css: yarn build:css --watch js: yarn build --reload # docker: docker-compose up worker: bundle exec sidekiq If you run Cartazzi and Poolwizard together then you're going to get crashes and here's the error: ❯ foreman start -f Procfile.dev 09:11:53 web.1 | started with pid 72877 09:11:53 css.1 | started with pid 72878 09:11:53 js.1 | started with pid 72879 09:11:53 worker.1 | started with pid 72881 09:11:53 js.1 | yarn run v1.22.5 09:11:53 css.1 | yarn run v1.22.5 09:11:53 css.1 | $ tailwindcss --postcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css --watch 09:11:53 js.1 | $ node esbuild.config.js --reload 09:11:54 js.1 | node:events:371 09:11:54 js.1 | throw er; // Unhandled 'error' event 09:11:54 js.1 | ^ 09:11:54 js.1 | 09:11:54 js.1 | Error: listen EADDRINUSE: address already in use :::5200 09:11:54 js.1 | at Server.setupListenHandle [as _listen2] (no ## Heroku Reports No Evidence of Unauthorized System or Customer Account Access Since April 14, 2022 DevFeed: [Heroku Reports No Evidence of Unauthorized System or Customer Account Access Since April 14, 2022]() Original publisher: [Read original article]() Author: Bob Wise Published: 2022-05-07T05:20:00Z Content type: news Language: en Sources: [Heroku]() Topics: [Heroku](), [incident](), [Security](), [GitHub](), [Deployment](), [Environment Variables](), [threat detection]() Tags: [deployment](), [environment-variables](), [github](), [heroku](), [incident](), [news](), [security](), [threat-detection]() ### AI overview Heroku says its investigation found no evidence of unauthorized access to Heroku systems since April 14, 2022, or access to customer accounts and decrypted environment variables. The company also addresses feedback about incident communications and says it plans to restore the GitHub integration when it is safe and secure. ### Source excerpt I started as Heroku GM a few weeks ago with intense enthusiasm to be a part of such a storied team. As you might expect, the last few weeks have not been what I would have imagined. But, contrary to what you might expect, I'm energized. I've been deeply impressed by the skills and dedication [...] The post We've Heard Your Feedback appeared first on Heroku. ## Automatically Authenticate with Preflight Scripts in Apollo Studio Explorer DevFeed: [Automatically Authenticate with Preflight Scripts in Apollo Studio Explorer]() Original publisher: [Read original article]() Author: Parul Schroff Published: 2022-01-12T08:36:16Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [Script](), [Authentication](), [GraphQL](), [OAuth](), [Code](), [Environment Variables]() Tags: [announcement](), [apollo](), [authentication](), [environment-variables](), [graphql](), [oauth](), [script]() ### AI overview This tutorial explains how to use Apollo Studio Explorer Preflight Scripts to run custom authentication before GraphQL operations. It covers configuring scripts for a graph variant, testing and publishing them, using environment variables, and refreshing OAuth access tokens. ### Source excerpt We recently introduced Preflight Scripts to Explorer! With preflight scripts you can automatically run any custom authentication before your GraphQL operation is executed. Preflight scripts are especially useful for managing authentication flows like OAuth by refreshing an access token, for example. Let's take a look. Setting up your preflight script For a graph and variant you want to create a script for, scroll down to find the "Preflight script" section in Apollo Studio Explorer Settings. ## Why it is time to get rid of passwords in our infrastructure DevFeed: [Why it is time to get rid of passwords in our infrastructure]() Original publisher: [Read original article]() Author: sasha@goteleport.com (Alexander Klizhentas) Published: 2021-11-19T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [passwords](), [Authentication](), [API keys](), [Security](), [Environment Variables](), [CI/CD]() Tags: [api-keys](), [authentication](), [ci-cd](), [environment-variables](), [passwords](), [security]() ### AI overview The article argues that passwords remain widespread in infrastructure, appearing as hardcoded credentials, API keys, tokens, cookies, second factors, environment variables, vault-mounted files, and CI/CD secrets. It explains that passwords can be guessed, intercepted, or stolen, and proposes examining supposedly passwordless alternatives more critically. ### Source excerpt Passwordless is a phrase generating a lot of buzz in the consumer space. But our infrastructure is full of passwords too and that needs to stop. ## Abusing and Detecting LOLBIN Usage of .NET Development Mode Features DevFeed: [Abusing and Detecting LOLBIN Usage of .NET Development Mode Features]() Original publisher: [Read original article]() Author: bohops Published: 2021-05-30T16:24:30Z Content type: tutorial Language: en Sources: [Bohops]() Topics: [.NET](), [configuration](), [Environment Variables](), [Development](), [Filesystems](), [Windows]() Tags: [configuration](), [debugging](), [development](), [environment-variables](), [files](), [microsoft](), [net](), [uncategorized](), [windows]() ### AI overview This article explains how .NET development-mode configuration can be abused to turn executables into living-off-the-land binaries by overriding Global Assembly Cache path lookups. It also discusses defensive detection considerations and shows the roles of configuration files and the DEVPATH environment variable. ### Source excerpt Background As discussed in this previous post, Microsoft has provided valuable (explicit and implicit) insight into the inner workings of the functional components of the .NET ecosystem through online documentation and by open-sourcing .NET Core. .NET, in general, is a very powerful and capable development platform and runtime framework for building and running .NET managed [...] ## Why I migrated to the Fish Shell DevFeed: [Why I migrated to the Fish Shell]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2020-12-07T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [friendly interactive shell](), [Shell](), [Zsh](), [Bash](), [dotfiles](), [Command-line interface](), [Environment Variables](), [lazy loading](), [Scripting]() Tags: [aliases](), [bash](), [environment-variables](), [lazy-loading](), [plugins](), [porting](), [prompt](), [scripting](), [shell](), [zsh]() ### AI overview The author explains migrating dotfiles from Zsh to Fish, emphasizing Fish's startup performance, universal variables, lazy loading, and built-in features such as syntax highlighting, autosuggestions, and man-page completions. The article also notes differences from POSIX shells and describes the author's plugin setup. ### Source excerpt Back in June, I started porting my dotfiles from ZSH to Fish. Here's why. ## Deploying to HatchBox with Rails 5.x DevFeed: [Deploying to HatchBox with Rails 5.x]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-09-14T13:22:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Environment Variables](), [PostgreSQL]() Tags: [deploy](), [environment-variables](), [hatchbox](), [postgresql](), [rails]() ### AI overview A tutorial on deploying a Rails 5.x application to HatchBox. It covers upgrading to Rails 5.2 when needed, configuring an existing PostgreSQL database and environment variables, creating Rails credentials, setting up a domain and Let's Encrypt SSL, and verifying the deployment. ### Source excerpt I just got a database less home page for a future SAAS app deployed via HatchBox under Rails 5.x and I thought the differences were significant enough that I should document it. HatchBox is the best tool I've ever found for Rails deploys but knowing all the steps to follow is key. elixi: Other than the Rails 5.2 upgrade step, there aren't many differences between this and Rails 6 but it has been long enough since I've done this that writing it down felt right. 1. Upgrade Rails to "5.2.x" if You Don't Have rails credentials:edit If your Rails 5 version is old enough that you get this crap: ❯ rails credentials:edit rails aborted! Don't know how to build task 'credentials:edit' (see --tasks) Here's the line you want to put into your Gemfile: gem 'rails', '~> 5.2' Once you change your Rails version, you want to use: bundle update to upgrade your Rails installation. 2. There is No True Database Less Deploy in HatchBox HatchBox is designed to work with a database (which is also the Rails default) because it calls database create and database migrate as part of the deploy. The trick here is to use an existing database and set your env variables and database.yml to allow for this Here's how to set up your database.yml file: production: adapter: postgresql url: <%= ENV['DATABASE_URL'] %> encoding: utf8 pool: 50 Your env variables are described in the section below. As long as you don't have migrations or database tables as part of your app, you can use any DATABASE_URL value (you set this below under environment variables; I just copied one from a different application). 4. Run rails credentials:edit The command: rails credentials:edit creates the Rails master key and secret key base that you need. You want to save your master key and secret key base because you need both in the env variables section. 5. HatchBox Setup You want to: Add your app to github or another supported version control system and note the username/repo_name pairing Create a new app Choose the cluster Ad ## Flat Multi-Environment Config for Craft CMS 3 DevFeed: [Flat Multi-Environment Config for Craft CMS 3]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-02-29T15:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [.env](), [Environment Variables](), [configuration](), [Development]() Tags: [aliases](), [api-keys](), [approach](), [article](), [cms](), [config](), [configs](), [craft](), [database](), [docker](), [environment](), [environment-variables](), [file](), [files](), [flat](), [git](), [heroku](), [insights](), [multi-environment](), [need](), [presents](), [secrets](), [sorts](), [variables]() ### AI overview A tutorial on configuring Craft CMS 3 across development, staging, and production environments using aliases, environment variables, .env files, and configuration files. It presents a flat configuration approach and discusses keeping environment-specific credentials and secrets separate from source code and databases. ### Source excerpt Multi-environment configs for Craft CMS are a mix of aliases, environment variables, and config files. This article sorts it all out, and presents a flat config file approach ## Cloud Build Recipes - Incrementing Build Numbers DevFeed: [Cloud Build Recipes - Incrementing Build Numbers]() Original publisher: [Read original article]() Published: 2019-02-01T03:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Google Cloud Platform (GCP)](), [ci](), [Android](), [Bash](), [Environment Variables](), [Disk image](), [Dockerfile]() Tags: [android](), [bash](), [ci](), [cloud](), [cloud-storage](), [docker](), [environment-variables]() ### AI overview A tutorial explains how to recreate incrementing CI build numbers in Google Cloud Build for Android app versioning. It uses a shared configuration folder, a text file, and Bash scripts to pass the updated number between isolated build steps, with an optional Docker container for deployment. ### Source excerpt Many CI services use an incrementing build number to identify builds. GCB, however, uses a randomly assigned unique identifier, as is common in large scale systems. While this is common and helps make GCB infinitely scalable, it makes it difficult to reason about the relationship between builds. Since I like to use the CI build number in my Android app versioning, I decided to reimplement this functionality using a simple script and text file stored in a shared location. The idea is simple, each build mounts a shared config folder, reads the version number from a text file, and overwrites that text file with a new version number. [Next page]()