ci/woodpecker/pr/config 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/web Pipeline was successful
ci/woodpecker/push/worker Pipeline was successful
Configuration
Web and worker use the same private config/hledger-reports.yaml. Start from the
example only for a new deployment;
never overwrite an existing journal selection or secrets.
journalselects the journal. Relative paths resolve from the configuration file; Docker needs the worker's container path.url.appis the exact browser origin. Configure one authentication strategy.accountsselects exact account names, optional display labels andcashorinvestmentregister 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:
pnpm config:validate --config /absolute/deployment/config/hledger-reports.yaml
The running web app serves the editor schema at /schema.json.