Local development, without an .env file.
The RDC CLI loads secrets into the child process environment when your command starts. Your app reads environment variables as usual.
Read the CLI guideYour secrets. Without the .env file.
Keep credentials in Envault and load them into your app when it runs. Use the same secret groups for local development and Container Engine deployments.
One source. Shared across applications.
Keep a common API key in a Shared group. Reference the keys your applications need, using the group, environment and key name.
Creating a Shared secret does not send it to every app. Each application chooses the keys it references; update the common value at its Shared source.
Shared source
payments-common / production
PAYMENTS_TOKEN••••••••Shared key references
Application Secrets
backend / production
PAYMENTS_TOKEN••••••••References payments-common / production
Application Secrets
worker / production
PAYMENTS_TOKEN••••••••References payments-common / production
Keep the next review in sight.
Set a review date on a secret. See upcoming and overdue reminders together, with Console notifications and email digests as the date approaches.
Shared secrets keep one reminder at the source, even when several applications use them. Reminders track review dates; they do not rotate or expire credentials.
Each app gets its own environments.
Organize application-specific keys in a group, then separate development and production. Keep database credentials local to that environment while reusing common keys from Shared Secrets.
Select the group and environment when linking a container or running a local process through the RDC CLI.
Set common defaults for your workspace.
Use Workspace Defaults for values every supported application container should receive, such as a common log level. Environment-specific credentials belong in Application Secrets.
Defaults apply when containers are created, started or redeployed. Application values and container-local overrides take precedence over the same default key.
Use the same configuration where you work.
Choose an Application environment for local development or link it to Container Engine. Envault resolves Shared references and combines defaults with application keys for delivery.
Link once. Apply on deployment.
Choose Link Envault in Container Engine and select a group and environment. After changing secrets, redeploy to apply the new values; a plain restart keeps the delivered configuration.
Explore Container Engine