Skip to Content

Deployment

Production deployment guidelines for atl-server.

Persistence

  • Persist ATL_DATABASE_PATH across restarts (it holds the log state and tree_uuid).
  • Persist ATL_SIGNING_KEY_PATH securely; rotating it changes signature identity (key ID).

Reverse proxy

  • Set ATL_BASE_URL to the public URL (scheme + host + optional port) so generated upgrade_url is reachable.
  • If you enable ATL_ACCESS_TOKENS, configure your clients to send Authorization: Bearer <token>.

Scaling

  • STANDALONE: simplest; one instance owns storage and sequencing.
  • NODE + SEQUENCER: scale out Nodes (HTTP) horizontally; keep a single Sequencer per log instance.

Health checks

  • GET /health exists only in node and sequencer modes.
    • Node reports gRPC connectivity to the Sequencer.
    • Sequencer reports storage availability.
Last updated on