Skip to content

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.

PageUse it for
HostingNode roles, scaling, image tags, and operator responsibilities
Deployment profilesThe three deployment models, what each survives, and how to move between them
ConfigurationMain configuration and secrets
Storage backendsThe object store and the node disk
SecurityListener exposure, hook signatures, and what Enroute does not isolate
MaintenanceAutomatic upkeep, ledger members, and recovery
ObservabilityTraces 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