Operate Enroute
Use these pages to deploy, configure, and maintain Enroute.
An Enroute deployment needs an object store and a durable local disk for each ledger node. It needs no external database. Expose the Git listener behind TLS. Keep the API listener reachable only by your application.
| Page | Use it for |
|---|---|
| Hosting | Node roles, scaling, image tags, and operator responsibilities |
| Deployment profiles | The three deployment models, what each survives, and how to move between them |
| Configuration | Main configuration and secrets |
| Storage backends | The object store and the node disk |
| Security | Listener exposure, hook signatures, and what Enroute does not isolate |
| Maintenance | Automatic upkeep, ledger members, and recovery |
| Observability | Traces and logs |
For a production deployment, read Hosting, Deployment profiles, Storage backends, and Security before Configuration. Then set up observability. Review Limitations before deploying.
Generated from docs/operate/README.md at bc0dc6e