bknd-env-config

To configure environment variables for a BKND project, you create a .env file at the project root and wire values into bknd.config.ts using the env parameter. The setup supports platform-specific variables for Cloudflare, Vercel, and Docker.

The best way to manage local overrides is by using .dev.vars files. This approach allows you to safely override environment variables during local development while enforcing strict production security requirements for your deployed BKND project.

You inject secrets into bknd.config.ts by passing them through the env parameter. The skill enforces production security requirements to ensure sensitive data like JWT_SECRET and DB_URL are validated and handled safely across deployment environments.

Yes, you can generate .env templates and sync secrets for Vercel or Docker. The skill provides centralized environment management with per-platform guidance and templates, ensuring your secrets are correctly formatted for each specific deployment target.

You need to validate production environment variables because the skill enforces production security requirements. This prevents missing or insecure secrets, such as an empty JWT_SECRET, from causing runtime failures or vulnerabilities in your deployed BKND application.