# Environment Variables Published articles for Environment Variables. 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 ## Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time DevFeed: [Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time]() Original publisher: [Read original article]() Author: Egor Klimov Published: 2026-09-16T12:34:47Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [OpenTelemetry](), [Microservices](), [observability](), [telemetry](), [Traces](), [ide]() Tags: [all-things-web](), [backstage](), [environment-variables](), [goland](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [jetbrains](), [microservices](), [observability](), [opentelemetry](), [performance-optimization](), [plugin-development](), [plugin-highlights](), [plugins](), [pycharm](), [research](), [rider](), [telemetry](), [traces](), [webstorm]() ### AI overview This article explains how the JetBrains OpenTelemetry Plugin generates a service map from runtime telemetry. It describes using logs, metrics, and especially standardized trace spans to visualize how microservices communicate, along with the plugin's lightweight local OpenTelemetry backend. ### Source excerpt We've all been there: you join a new project, and the first thing you ask for is the architecture diagram. You're handed a diagram that looks great, but after a week of debugging, you realize it's six months out of date. Service A hasn't talked to Service B since the spring, and there's a new [...] ## 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 ## How to Connect Your Twilio Agent to External APIs DevFeed: [How to Connect Your Twilio Agent to External APIs]() Original publisher: [Read original article]() Author: Amanda Lange Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [AI Agent](), [API](), [C#](), [.NET 9](), [REST API](), [SDKs](), [OpenAI]() Tags: [agent](), [api](), [apis](), [c-sharp](), [developer-insights](), [environment-variables](), [how-to](), [net](), [net-9](), [ngrok](), [openai](), [rest-api](), [sdk]() ### AI overview This tutorial explains how to build a voice AI agent with C# and .NET 9 using Twilio Conversation Relay. It demonstrates LLM tool calling to fetch live data from an external REST API and covers project setup, required packages, environment variables, and API key storage. ### Source excerpt How to Connect Your Twilio Agent to External APIs ## How to Connect Your Twilio Agent to External APIs in Node.js DevFeed: [How to Connect Your Twilio Agent to External APIs in Node.js]() Original publisher: [Read original article]() Author: Dhruv Patel, Amanda Lange Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [AI Agent](), [Node.js](), [voice ai](), [REST API](), [OpenAI](), [Express]() Tags: [agent](), [ai](), [ai-agent](), [developer-insights](), [environment-variables](), [node-js](), [openai](), [rest-apis](), [visual-studio-code](), [voice]() ### AI overview This tutorial explains how to build a voice-enabled AI agent in Node.js with Twilio Conversation Relay and OpenAI. The agent uses LLM-driven tool calling to retrieve live data and take actions through an external REST API. ### Source excerpt Build a voice-enabled AI agent in Node.js with Twilio Conversation Relay and OpenAI to dynamically fetch live data from external REST APIs. ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory]() Original publisher: [Read original article]() Author: Amanda Lange, Dhruv Patel Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Node.js](), [Large Language Model](), [Express](), [OpenAI](), [API](), [WebSocket](), [Machine learning]() Tags: [api](), [axios](), [console](), [developer-insights](), [environment-variables](), [express](), [how-to](), [http](), [ide](), [install](), [js](), [json](), [llm](), [ngrok](), [node-js](), [npm](), [openai](), [rest-api](), [sdk](), [visual-studio-code](), [web]() ### AI overview This tutorial shows how to build a Node.js Express service that uses Twilio Conversation Memory, OpenAI, and voice streams to preserve caller context, preferences, and action history across separate inbound calls. It covers project setup, package installation, local webhook exposure with ngrok, and access to Twilio's Conversation Memory REST API. ### Source excerpt Learn how to orchestrate multi-call voice conversations using Node.js, OpenAI, and Twilio Conversation Memory to persist caller context across separate calls. ## OpenTelemetry proposes environment variables for context propagation across processes DevFeed: [OpenTelemetry proposes environment variables for context propagation across processes]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-09-11T11:01:22Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [context](), [tracing](), [OpenTelemetry](), [Processes](), [CI/CD](), [data-processing]() Tags: [ci-cd](), [data-processing](), [environment-variables](), [opentelemetry](), [processes](), [spans](), [tracing](), [w3c]() ### AI overview The OpenTelemetry Specification has a release candidate for using environment variables to carry trace context and baggage between processes. The article explains how this can connect spans across workflow runners, shells, build tools, test processes, and similar workloads when protocol headers or message metadata are unavailable, and requests feedback before the specification becomes Stable. ### Source excerpt A trace does not always cross a network boundary. A workflow runner starts a shell, the shell launches a build tool, and the build tool starts test processes. Batch and data-processing systems create similar chains of child processes. Without a shared way to pass trace information across these boundaries, spans from each process can end up in separate traces. If context propagation is new to you, it is the mechanism that carries information from one service or process to the next. For tracing, this includes the trace and span identifiers that let new spans join the same trace. It can also carry baggage: application-defined key-value pairs that are passed to downstream work. ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory with PHP DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory with PHP]() Original publisher: [Read original article]() Author: Amanda Lange, Matthew Setter Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Composer](), [Large Language Model](), [context](), [PHP](), [Tutorial](), [Orchestration](), [OpenAI]() Tags: [agent](), [ai](), [api](), [code](), [context](), [conversation-memory](), [developer-insights](), [environment-variables](), [how-to](), [llm](), [logging](), [ngrok](), [orchestration](), [php](), [phpstorm](), [voice-api]() ### AI overview This tutorial shows how to build a PHP service with Open Swoole that uses Twilio Conversation Memory to preserve caller context, preferences, and action history across separate inbound calls. It covers the required accounts, tools, environment variables, Composer setup, OpenAI integration, logging, and Memory Store configuration. ### Source excerpt In this tutorial you'll make a PHP service using Open Swoole that retains caller context, preferences and action history across multiple separate inbound calls. ## 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. ## How to Use Svelte and Go to Build a Video Chat App DevFeed: [How to Use Svelte and Go to Build a Video Chat App]() Original publisher: [Read original article]() Author: Donal Toomey Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Svelte](), [Go Language](), [Vite](), [REST API](), [Single-page application (SPA)](), [Back end](), [Front end]() Tags: [api](), [build-video-app](), [build-video-chat-app](), [cors](), [developer-insights](), [env-file-security](), [environment-variables](), [git](), [go](), [how-can-i-build-a-video-app](), [how-to](), [how-to-create-video-chat-app](), [how-to-make-video-chat-app](), [live-video-chat-app](), [node-js](), [npm](), [real-time](), [svelte](), [twilio-golang](), [twilio-programmable-video](), [twilio-video](), [twilio-video-tutorial](), [video-api](), [video-app](), [video-chat-app](), [vite]() ### AI overview This tutorial explains how to build a real-time video chat app using Svelte for the frontend, Go for the backend, and the Twilio Video API. It covers the application flow, project setup, dependencies, environment configuration, and credential handling. ### Source excerpt Build a real-time video chat app with Svelte 5, Vite, and Go using the Twilio Video API. ## Pulumi v3.254.0 Adds Automatic Encrypted Logging DevFeed: [Pulumi v3.254.0 Adds Automatic Encrypted Logging]() Original publisher: [Read original article]() Author: Thomas Gummerer Published: 2026-08-10T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Logging](), [debugging](), [Encryption]() Tags: [debugging](), [encryption](), [environment-variables](), [features](), [github](), [logging](), [logs](), [observability](), [product]() ### AI overview Pulumi v3.254.0 automatically creates encrypted log files for every operation, allowing users to share existing logs with the Pulumi team for debugging. Logs use AES256-GCM encryption, rotate after seven days or when they reach 500 MB, and can be decrypted locally with pulumi logs decrypt. ### Source excerpt Pulumi v3.254.0 introduces automatic logging: every operation is logged in an encrypted log file that can optionally be shared with the Pulumi team for inspection. No more re-running commands just to get logs to the Pulumi team for debugging; instead you can share existing logs securely. You might have been in a situation where pulumi hit an error for an unexpected reason, or did something that was not quite right. Currently the process for trying to resolve that is to try and reproduce the error, ideally now with logging enabled. Sometimes the error doesn't reproduce, or the state pulumi was in at the time of the error doesn't exist anymore. And even if the issue reproduces it's a bit of a hassle to do all this again, just to get logs to Pulumi employees who can do something with them. There's also no great mechanism to send the potentially sensitive log file. How it works From pulumi v3.254.0 onward, we automatically produce log files for every operation and store them in $PULUMI_HOME/logs. These log files are encrypted on disk, using the relevant stack's secret manager, whenever it is available, as they still contain secrets at this point. The final file consists of gzip'd chunks that are encrypted using AES256-GCM. Log files are gzip'd when no secrets manager is available, as no secrets from property values can be in the log at that point. Note that the logs are rotated out after 7 days, or after the log directory has reached 500 MB, removing the oldest logs first. This way logs will never fill up your disk, but will still be available after running pulumi commands. These defaults can be overridden with the PULUMI_LOG_ROTATION_MAX_AGE_DAYS and PULUMI_LOG_ROTATION_MAX_TOTAL_MB environment variables. Locally these logs can be decrypted using pulumi logs decrypt. For this to work the same stack's secret manager as was used for the command needs to be available. Sharing logs Previously there was no good way to securely share the logs with us. Users were always force ## Managing Environment Variables and Secrets in DevOps DevFeed: [Managing Environment Variables and Secrets in DevOps]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-01T13:00:47Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [DevOps](), [configuration](), [GitGuardian](), [GitHub](), [Terraform](), [Kubernetes]() Tags: [ci-cd-secrets-management](), [cloud](), [collaboration](), [collaboration-tools](), [configuration](), [container](), [crash](), [devops](), [devsecops](), [dynamic-secrets](), [env-file-security](), [environment-variables](), [gitguardian](), [github](), [hardcoded-credentials](), [hashicorp-vault](), [jira](), [kubernetes](), [kubernetes-secrets](), [leak](), [managing-environment-variables-and-secrets](), [rotation](), [safety](), [sealed-secrets](), [secret-rotation](), [secret-scanning](), [secrets](), [secrets-management-best-practices](), [security](), [storage](), [terraform](), [vault]() ### AI overview A guide to managing environment variables and secrets in DevOps. It explains how secrets escape through repositories, processes, crash reports, containers, collaboration tools, Kubernetes Secrets, and Terraform state, and discusses storage, access controls, lifecycles, and rotation. ### Source excerpt Nearly 29 million secrets were pushed to public GitHub in a single year, and most teams still discover their own leaks by accident. Here is how environment variables actually escape, and what to use instead at each stage. ## The Appwrite MCP server is now remote: one URL, no API keys DevFeed: [The Appwrite MCP server is now remote: one URL, no API keys]() Original publisher: [Read original article]() Author: Aditya Oberai Published: 2026-07-31T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [MCP Server](), [Model Context Protocol](), [OAuth](), [Claude Code](), [cursor](), [codex]() Tags: [ai-coding-agents](), [claude](), [claude-code](), [cursor](), [environment-variables](), [mcp](), [mcp-server](), [oauth](), [products](), [remote](), [vs-code]() ### AI overview Appwrite announces that its MCP server is now available as a hosted remote server for Appwrite Cloud users. Developers can connect AI coding tools with one URL and authenticate through OAuth, without local installation or API keys. The server also includes Appwrite documentation search. ### Source excerpt The Appwrite MCP server is now a hosted remote server. Add one URL to your AI tool, sign in with OAuth, and start building. No installs, no API keys, nothing to keep updated. ## One-command OpenTelemetry setup on Linux hosts DevFeed: [One-command OpenTelemetry setup on Linux hosts]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-23T16:51:56Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [Linux](), [Automation](), [systems]() Tags: [automation](), [aws-lambda](), [environment-variables](), [installation](), [java](), [linux](), [monitoring](), [net](), [node-js](), [opentelemetry](), [packaging](), [processes](), [python](), [setup]() ### AI overview OpenTelemetry introduces a package-based setup for instrumenting Java, .NET, Node.js, and Python applications running directly on Linux hosts. The package installs the OpenTelemetry Injector, SDKs, and auto-instrumentation packages, which activate instrumentation at process startup without application code or deployment-script changes. ### Source excerpt OpenTelemetry as system dependency Setting up OpenTelemetry for your applications and systems depends on where those apps and systems run. Some are very automated, especially Kubernetes, thanks to the OpenTelemetry Operator, or AWS Lambda, with the OpenTelemetry Lambda layers. But the countless Java, .NET, Node.js, and Python apps running directly on Linux hosts have had no such automation. Instrumenting those has meant downloading agents by hand and wiring up environment variables yourself. At OTel Unplugged EU in Brussels this February, one ask kept coming up: clear packaging, installation, and usage paths. You asked for: ## 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 ## Cloud native application challenges: installing the walking skeleton DevFeed: [Cloud native application challenges: installing the walking skeleton]() Original publisher: [Read original article]() Author: Manning Book Authors Published: 2026-05-13T13:00:00Z Content type: tutorial Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [YAML](), [Containers](), [Platform Engineering]() Tags: [applications](), [article](), [chronosphere](), [cloud-native-ecosystem](), [configuration](), [container](), [engineering](), [environment-variables](), [kubernetes](), [platform](), [platform-engineering](), [post-contributed](), [secrets](), [sponsor-chronosphere](), [sponsored-post-contributed](), [yaml]() ### AI overview This excerpt from Platform Engineering on Kubernetes explains how Kubernetes YAML defines and configures containerized applications. It introduces Deployments, Services, Ingress, and ConfigMaps or secrets, including their roles in replication, traffic routing, service discovery, and configuration management. ### Source excerpt Editor's note: This article is an excerpt from Chapter 1 of the Manning book, Platform Engineering on Kubernetes. This excerpt The post Cloud native application challenges: installing the walking skeleton appeared first on The New Stack. ## Sending mission-critical emails in Python: SMTP or API? DevFeed: [Sending mission-critical emails in Python: SMTP or API?]() Original publisher: [Read original article]() Author: Greg Svoboda (gsvoboda@activecampaign.com) Published: 2026-04-29T15:24:00Z Content type: tutorial Language: en Sources: [Postmark (en-US)]() Topics: [Python](), [API](), [Protocol (disambiguation)](), [servers](), [Library]() Tags: [api](), [code](), [email-delivery](), [environment-variables](), [library](), [protocol](), [python](), [server](), [third-party]() ### AI overview This tutorial compares sending email from Python applications through SMTP versus an email provider's API. It explains SMTP's quick setup and portability, while noting scalability, spam-flag, troubleshooting, and functionality tradeoffs associated with each approach. ### Source excerpt If you need to send emails from an application, it's a good idea to think about how your usage changes over time. As with many technology choices, there's a tradeoff between up-front efficiency and long-term flexibility. You have two main choices for sending emails through your Python application. The first is SMTP -- the standard protocol for outgoing email. The second option sidesteps SMTP's complexities by using an email provider's API for richer functionality. This article compares sending email in Python using SMTP and API. SMTP is quick to set up--especially with a library like smtplib--but it won't scale as your app grows, puts you at risk of spam flags, and makes diagnosing problems complex. An API setup takes a little longer, but it yields dividends with features you can leverage in many ways. Go lean with SMTP SMTP is a basic, universal protocol for sending email. Direct SMTP implementation is as close as you can get to DIY email, but even the simplest sending setup still requires a third-party SMTP server. Technically speaking, you could host your own SMTP server, but it's rarely a good tradeoff. Inbox providers pay close attention to sender reputation to determine which emails make it through. An established SMTP service helps ensure your emails are actually delivered. The code below uses the Postmark SMTP servers. Start fast with common tools (like smtplib) Sending email with SMTP is straightforward and very similar in any application. Once set up, the advantage is that you can try a new service without completely overhauling your application -- you can change SMTP service providers using the same code. To implement SMTP in a Python application, use the built-in library called smtplib and follow these steps: 1. Import smtplib You don't need to install any new libraries -- the SMTP module is included when you install Python. Just import it, along with MIMEText, which helps with email formatting: import smtplib from email.mime.text import MIMEText 2. Set up yo ## Deploying Temporal Workers to Amazon ECS DevFeed: [Deploying Temporal Workers to Amazon ECS]() Original publisher: [Read original article]() Author: Ebenezer Ankrah Published: 2026-04-02T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Amazon Elastic Container Service](), [Deployment](), [AWS IAM](), [Dockerfile](), [container](), [health checks](), [Amazon Web Services]() Tags: [amazon](), [deployment](), [docker](), [docker-image](), [ecs](), [environment-variables](), [health-checks](), [how-to](), [iam]() ### AI overview A guide to deploying Temporal Workers on Amazon ECS with Fargate. It explains container configuration, health checks, graceful shutdown, task definitions, IAM roles, secret injection through SSM Parameter Store, and outbound connectivity requirements. ### Source excerpt A comprehensive guide to deploying Temporal Workers on Amazon ECS with Fargate. Covers container config, IAM roles, scaling, and cost-saving with Fargate Spot. ## AI sandboxes & volumes: isolated environments for coding agents DevFeed: [AI sandboxes & volumes: isolated environments for coding agents]() Original publisher: [Read original article]() Author: Ruben Fiszel Published: 2026-04-01T00:00:00Z Content type: article Language: en Sources: [Windmill Blog]() Topics: [AI Sandbox](), [AI-assisted coding](), [Claude Code](), [codex](), [Persistence](), [Authorization]() Tags: [agents](), [ai](), [claude-code](), [codex](), [coding-agents](), [environment-variables](), [launch-week](), [permission](), [persistence](), [sandboxes](), [scope](), [volumes]() ### AI overview Windmill introduces AI sandboxes that run Claude Code, Codex, and custom agents in isolated environments with persistent volumes. The article explains how annotations provide process isolation and storage, including synchronization with object storage, exclusive volume leases, caching, and per-user or per-group permissions. ### Source excerpt Introducing AI sandboxes: run Claude Code, Codex, or custom agents in isolated environments with persistent volumes on Windmill. ## Migrating from GitHub Pages to Netlify in an Evening DevFeed: [Migrating from GitHub Pages to Netlify in an Evening]() Original publisher: [Read original article]() Published: 2026-03-25T00:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [migration](), [GitHub Pages](), [Netlify](), [GitHub](), [GitHub Actions](), [hosting](), [Astro]() Tags: [astro](), [dns](), [environment-variables](), [github](), [github-actions](), [github-pages](), [hosting](), [migration](), [netlify](), [secrets](), [ssl](), [workflow]() ### AI overview A first-person guide to migrating a static Astro blog from GitHub Pages to Netlify. It covers connecting the repository, transferring environment variables, moving DNS and SSL, restoring Mailgun email-forwarding records, and replacing a scheduled GitHub Actions rebuild with a Netlify build hook. ### Source excerpt Another hosting migration I'd been putting off for years, done in 30 minutes with Claude Code. ## 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 ## App Hosting has in-console environment variables and faster builds DevFeed: [App Hosting has in-console environment variables and faster builds]() Original publisher: [Read original article]() Author: Julia Reid Published: 2026-03-12T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [hosting](), [build performance](), [configuration](), [Deployment]() Tags: [app-hosting](), [build-times](), [cloud-native](), [configuration](), [deployment](), [environment-variables](), [firebase](), [firebase-console](), [javascript](), [web]() ### AI overview Firebase App Hosting now supports adding and editing environment variables in the Firebase console. The update also describes configuration merging, precedence rules, secret references, and an optimized build process intended to improve build times. ### Source excerpt Manage environment variables in the Firebase console, and learn about a small change our engineering team made to improve build times for everyone. [Next page]()