env

Configures Kamal deploy.yml environment variables and secret management with per-host tags and role-specific settings.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/donnfelker/kamal-skills --skill env-donnfelker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env
Source: https://github.com/donnfelker/kamal-skills/tree/main/skills/env
Command: npx skills add https://github.com/donnfelker/kamal-skills --skill env-donnfelker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the complexity of managing environment variables in Kamal deployments by providing a structured, secure way to separate plain configuration from sensitive secrets.

Core Features & Use Cases

  • Secure Secret Handling: Implements best practices for keeping sensitive data out of version control using .kamal/secrets and password-manager integration.
  • Contextual Configuration: Supports per-host overrides via tags and per-role environment variables for complex multi-server architectures.
  • Use Case: Use this to safely inject database passwords and API keys into your production environment without exposing them in your git repository.

Quick Start

Ask the agent to configure the environment variables for your Kamal deployment by specifying which values are clear and which should be treated as secrets.

Frequently Asked Questions about env

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

FAQPage Schema
What is the best way to configure per-host and per-role environment variables in Kamal?

Configuring per-host and per-role environment variables in Kamal involves using specific host tags and role-specific settings within your deploy.yml file. This allows complex multi-server architectures to receive contextual configuration tailored to each server's distinct operational role.

How do Kamal dotenv loading patterns handle secret references?

Kamal dotenv loading patterns handle secret references by requiring adherence to secure handling practices that pull sensitive values from external sources like password managers. This mechanism injects clear values and secret references directly into your deployment environment safely.

Can I use password-manager integration for Kamal secret management?

Yes, you can use password-manager integration for Kamal secret management to securely handle sensitive data. This approach implements best practices for keeping credentials out of your git repository by securely pulling database passwords and API keys during deployment.

How do I inject database passwords without exposing them in my git repository using Kamal?

To inject database passwords safely without git repository exposure, you use Kamal's structured secret handling via .kamal/secrets files. This separates sensitive deployment configuration from version control by referencing external secret stores during deployment.