Files
eleith 5437202774
ci/woodpecker/pr/config Pipeline was successful
ci/woodpecker/pr/hledger Pipeline was successful
ci/woodpecker/pr/jobs Pipeline was successful
ci/woodpecker/pr/snapshots Pipeline was successful
ci/woodpecker/pr/web Pipeline was successful
ci/woodpecker/pr/worker Pipeline was successful
ci/woodpecker/push/config Pipeline was successful
ci/woodpecker/push/hledger Pipeline was successful
ci/woodpecker/push/jobs Pipeline was successful
ci/woodpecker/push/snapshots Pipeline was successful
ci/woodpecker/push/web Pipeline was successful
ci/woodpecker/push/worker Pipeline was successful
refactor: clarify report ownership and simplify docs and tests
2026-11-07 09:44:46 -08:00

24 lines
1.2 KiB
Markdown

# Configuration
Web and worker use the same private `config/hledger-reports.yaml`. Start from the
[example](../../apps/web/config/hledger-reports.example.yaml) only for a new deployment;
never overwrite an existing journal selection or secrets.
- `journal` selects the journal. Relative paths resolve from the configuration file; Docker needs the worker's container path.
- `url.app` is the exact browser origin. Configure one [authentication strategy](../../docs/authentication.md).
- `accounts` selects exact account names, optional display labels and `cash` or `investment` register membership. Labels and names are literal; membership is presentation, not authorization or journal scope.
Environment references support `${NAME}` and `${NAME:-fallback}`. Account names
and labels are not expanded. Restart services after changes.
Data lives in the sibling `data/` directory beside `config/`; web and worker must
select the same deployment. Do not move or replace existing data to change labels.
Validate configuration without reading the journal:
```sh
pnpm config:validate --config /absolute/deployment/config/hledger-reports.yaml
```
The running web app serves the editor schema at `/schema.json`.