render-env-vars

Configures environment variables, secrets, and env groups on Render services.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-env-vars-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-env-vars
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-env-vars
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-env-vars-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing environment variables and secrets across Render services is error-prone: values are always strings, Blueprint and Dashboard behavior diverge, and miswired references cause runtime failures. This Skill provides authoritative guidance for setting, wiring, and debugging env vars on Render. ## Core Features & Use Cases - Three configuration paths: Covers Dashboard edits, Blueprint envVars in render.yaml, and MCP/API automation for CI-driven secret rotation. - Secret management patterns: Explains generateValue: true, sync: false behavior, secret files under /etc/secrets/, and environment group precedence rules. - Blueprint wiring reference: Documents fromDatabase, fromService, and fromGroup patterns with complete YAML examples, plus platform-injected variables like PORT and RENDER_*. - Use Case: You are deploying a Node.js API on Render that needs a Postgres connection string, a Redis URL, and a third-party API key. Use this Skill to wire fromDatabase and fromService references in render.yaml and mark the API key as sync: false so it is never committed to Git. ## Quick Start Ask the assistant to wire a DATABASE_URL from a Render Postgres database and a generated session secret into your render.yaml service definition.

Frequently Asked Questions about render-env-vars

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set environment variables on Render?▼

Set environment variables on Render through the Dashboard UI, the envVars section of render.yaml in a Blueprint, or the MCP/API for automation. Dashboard supports individual entries and bulk .env imports, while Blueprints support references to databases, services, and env groups.

How do I add secrets to a Render Blueprint without committing them?▼

Use generateValue: true to have Render create a base64-encoded 256-bit random value, or sync: false to prompt for the value in the Dashboard on initial creation. Never place real secrets as plain value entries in render.yaml.

Does sync: false re-prompt for values on Blueprint updates?▼

No, sync: false only prompts in the Dashboard when the Blueprint first creates the service. On subsequent render.yaml updates the prompt is ignored, and these variables are excluded from preview environments and invalid inside environment groups.

How do I connect a Render service to a Postgres database?▼

Use a fromDatabase reference in envVars pointing to the database name and a property such as connectionString, host, port, user, password, or database. The database must exist in the same Blueprint or already exist in the same Render workspace.

Why is my Render environment variable behaving unexpectedly?▼

All Render environment variables are strings, so values like DEBUG=false may be truthy in your parser. Also check precedence: service-level variables override environment group variables, and secret files must be read from /etc/secrets/<filename>.

What port should my web service bind to on Render?▼

Bind your HTTP server to 0.0.0.0 and the PORT environment variable, which defaults to 10000 on Render. Some stacks set their own conventions, such as Gunicorn binding to 0.0.0.0:10000 via GUNICORN_CMD_ARGS.