Skip to content

integration-proxy: host-agnostic deployment docs (non-Heroku, local Postgres, SESSION_SECRET) #79

Closed

Description

@michielbdejong

The README and deploy notes assume Heroku: a Procfile, and DATABASE_URL coming from the Postgres add-on. atomic-saas is going to run the proxy on Hetzner, as a systemd service behind Caddy with a Postgres on the same host. Nothing in src/ needs to change for that, but the docs, and possibly CI, should treat Heroku as one option rather than the only one.

Proposed changes

  • README: a "Deploying" section that doesn't depend on the host.
    • What the process needs: the env vars, one HTTP port, Postgres, and an https BASE_URL, since session cookies are Secure.
    • GET /healthz is the health check.
    • Heroku becomes one example (the Procfile), and a plain systemd unit another.
  • Document Postgres TLS. security.rs always uses a verifying native_tls connector. Heroku's managed Postgres presents a valid certificate. A local, loopback-only Postgres typically has TLS off, so the docs should say to set ?sslmode=disable in DATABASE_URL for that case, and to never use it across a network.
    • Worth adding a CI test (the existing postgres:16-alpine service runs without TLS) that confirms a sslmode=disable URL connects.
  • Document the SESSION_SECRET requirement. Without it, a random key is generated on every start, and every deploy logs everyone out. This should be required in production, or at least warned about loudly at startup.
  • Optional: release binaries. A CI job that builds a static x86_64-unknown-linux-musl binary and attaches it to a GitHub release on tag. Other hosts could then deploy without a Rust toolchain. atomic-saas doesn't need this if the lib split in the companion issue lands, because it will build from source.

Context

  • The login side is already generic OIDC (APP_AUTH_*). atomic-saas will add authorize, token and userinfo endpoints so that its existing magic-link and passkey session can be the proxy's login.
  • sub will be a stable user id, not an email address, because it feeds the tenant secret.

Activity

  1. michielbdejong commented on Sep 23, 2026

    @michielbdejong
    ContributorAuthor

    Direction update: see ontola/atomic-server#1650. The proxy is heading into atomic-server behind a Cargo feature, with a storage trait so embedded builds don't need Postgres. Host-agnostic deployment docs still matter for the standalone binary (the hosted fallback instance), and the SESSION_SECRET and sslmode points still apply to it.

  2. michielbdejong commented on Sep 24, 2026

    @michielbdejong
    ContributorAuthor

    Picked up by the atomic-plugins oversight session (e6ce43). Per Michiel's decision on ontola/atomic-server#1700 (answer 6), self-hosted atomic-servers default to atomic.place's proxy, and the connect UI links to a public self-hosting guide. That guide is this issue's deliverable, at the fixed path integration-proxy/SELF_HOSTING.md: https://github.com/ontola/atomic-plugins/blob/main/integration-proxy/SELF_HOSTING.md. A worker agent is writing it and fixing the stale Heroku-specific bits in the README.

  3. added a commit that references this issue on Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions