Configuring Your Installation
After the Full Stack Quick Start, every service runs with starter values: shared secrets, bundled infrastructure, and settings chosen for a first run. This section takes you from that starting point to an installation you control.
How each service is configured
| Service | Configured with |
|---|---|
| Core | YAML configuration files, overridden by ONE_ environment variables |
| BFF, Bridge, WRPR | Spring Boot properties, with defaults in the image, overridden by environment variables |
| oauth2-proxy, Keycloak, Traefik, databases, Redis | Their own configuration formats; see each project's documentation |
For how configuration layers are combined, and other ways to configure the services, see Configuration Mechanics.
Making changes
The pages in this section give each change as an environment variable. Add or change the variable in the service's environment file from the quick start bundle:
| Service | Environment file |
|---|---|
| Core | env/.core.env |
| BFF | env/.bff.env |
| Bridge | env/.bridge.env |
| WRPR | env/.wrpr.env |
| Keycloak | env/.keycloak.env |
| Databases | env/.core_mariadb.env, env/.bff_mariadb.env, and so on |
Then apply the change:
docker compose up -d
Compose recreates only the services whose environment changed.
Variable names are case-sensitive, and a misspelled name is ignored without an error. If a change has no effect, check the name first.
A few changes are made in other files, such as the oauth2-proxy configuration. The pages that cover them say where.
Example: Core log level
The quick start runs Core with debug logging. To reduce it, add this line
to env/.core.env:
ONE_app__traceLevel="info"
Apply the change and follow the Core logs:
docker compose up -d
docker compose logs -f core
Debug messages no longer appear.
Next steps
Work through the pages in this section to replace the starter setup with your own domain, secrets, and infrastructure.