render-env-vars

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

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/greenmartialarts/EventCore --skill render-env-vars-greenmartialarts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-env-vars
Source: https://github.com/greenmartialarts/EventCore/tree/main/.junie/skills/render-env-vars
Command: npx skills add https://github.com/greenmartialarts/EventCore --skill render-env-vars-greenmartialarts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing environment variables across Render services is error-prone: values arrive as strings, secrets risk being committed to Git, and Blueprint wiring patterns like sync: false and fromService behave in non-obvious ways. This Skill provides authoritative guidance for setting, wiring, and debugging environment configuration on Render. ## Core Features & Use Cases - Three configuration paths: Covers Dashboard edits (individual or bulk .env import), Blueprint envVars in render.yaml, and MCP/API automation for CI-driven secret rotation. - Secret management patterns: Explains generateValue: true for platform-generated 256-bit secrets, sync: false for Dashboard-prompted values, and secret files mounted at /etc/secrets/<filename>. - Blueprint wiring reference: Documents fromDatabase, fromService, and fromGroup patterns with YAML examples, plus precedence rules where service-level vars override group vars. - Use Case: You are deploying a Fastify API that needs a database connection string, a Redis URL, and a third-party API key. Use this Skill to wire DATABASE_URL via fromDatabase, REDIS_URL via fromService, and the API key via sync: false without committing secrets to Git. ## Quick Start Ask the assistant to configure a DATABASE_URL environment variable on your Render web service using a Blueprint fromDatabase reference.

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 three ways: individually or in bulk through the Render Dashboard, declaratively via envVars in a render.yaml Blueprint, or programmatically through the API/MCP tools. Dashboard edits suit quick iteration, while Blueprints keep configuration version-controlled.

How do I add secrets to Render without committing them to Git?

Use generateValue: true for platform-generated 256-bit random secrets, or sync: false to prompt for the value in the Dashboard on initial Blueprint 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. Subsequent render.yaml updates ignore sync: false entries, and these variables are excluded from preview environments and invalid inside environment groups.

How do I share environment variables across multiple Render services?

Use environment groups, which are named variable collections linked to multiple services via fromGroup in a Blueprint. Service-level variables override group variables with the same name, so define shared defaults in the group and service-specific overrides directly.

Why is my boolean environment variable not working on Render?

All Render environment variables arrive as strings, so DEBUG=false is truthy in many parsers. Parse values explicitly with typed config loaders or direct string comparison instead of relying on implicit boolean coercion.

Where are secret files mounted on Render services?

Secret files appear as plaintext files under /etc/secrets/<filename> on the running instance, including Docker-based services. The combined secret file payload is limited to 1 MB per service or linked environment group.