Configuration

Where configuration comes from

This repo ships no workload chart — the orchestration repo renders this location’s runtime environment when the location is registered. Configuration reaches the running code as environment variables, layered from Doppler:

1. global/prd — shared values (databases, email, …)
2. each declared Doppler dependency project
3. betting-combat/prd — this location’s own project

Later layers win on key conflicts. To add or change a value, edit it in Doppler — the platform auto-publishes a ClusterSecretStore per Doppler project, so a new project needs no platform edit.

Create betting-combat/prd before registration. The platform’s scheduled sync discovers new projects automatically; dispatch its secret-stores-sync workflow when the store is needed immediately.

Local development

Copy .env.example to .env and fill in what dagster dev needs locally. .env is git-ignored; nothing secret ever lands in the repo.

Variable	Description	Default
APP_ENV	Environment name	development
LOG_LEVEL	Logging level	INFO