Configuration

Keep project configuration inspectable. Orjanda applications use orjanda.yaml alongside environment-specific values.

The configuration file

orjanda.yaml is the project-level configuration file. Commit the stable shape of your application here, and keep secrets out of source control.

# Project configuration
# Keep release-supported keys from your v0.1.5 project here.
 
# environment-specific values belong in your environment
# rather than in the repository

Environment values

Use environment variables for values that change between development and production, especially credentials and deployment-specific settings. This release’s supplied materials do not define a canonical variable list, so this guide intentionally avoids inventing names.

A safe workflow

Start with the generated project, make one configuration change at a time, and run orjanda serve locally before promoting it. Keep local overrides private and make the production configuration reproducible.