Developer
Environment Configuration

Environment Configuration

Keep environment-specific configuration outside source control.

Local development

Configure the local backend with only the services required for the feature you are developing or testing. Typical categories include:

  • the local database connection;
  • optional queue or cache services;
  • local authentication and integration settings;
  • public browser configuration used by the web application.

Use development-only values. Do not reuse production credentials in a local environment.

Secret handling

Never place passwords, API credentials, signing material, database credentials, or third-party service secrets in documentation.

Keep secret values in the local environment or an approved secret-management mechanism. Commit only documented placeholders or templates that are explicitly intended for source control.

Browser-visible configuration must never contain server-side secrets.

Environment separation

Use separate configuration for development, staging, and production. A local development command should not depend on production-only values.

Next step

Continue with PostgreSQL Bootstrap.