Epure
Guide

Epure production Compose overlay

Overlay + env vars: secrets, PUBLIC_URL, Postgres off the host port, health checks. Two services. You own TLS and backups.

On this pageShow
  1. Topology
  2. Env checklist
  3. Overlay up
  4. Health
  5. What you still own
  6. Questions

This page is the overlay and env runbook. For the full small-VPS path (DNS, TLS install, first user), use Cheap VPS install.

Topology

Internet -> TLS edge -> Epure app -> PostgreSQL 16

No Redis. No Kafka. No ClickHouse as defaults.

Env checklist

  • Strong SECRET / admin bootstrap values per install docs.
  • PUBLIC_URL = public HTTPS origin clients use in the DSN host.
  • Postgres credentials in Compose secrets/env; not published to 0.0.0.0.
  • Resource limits optional; prefer measuring on your box.

Follow Installation for current variable names on your image tag.

Overlay up

docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d

docker compose ps

docker compose logs -f --tail=100

If your checkout uses deploy/ templates (Coolify or prod examples), prefer those files over inventing new names.

Health

GET /health must return ok before you point production DSNs. Then register and copy a project DSN.

What you still own

TLS certificates, DNS, Postgres backups, image upgrades, disk, and reading logs. Sibling guides: Cheap VPS install, Backups and upgrades.

Questions

Why two containers?
App and database separation. SQLite-as-primary is not the Epure default.
Is Cloud easier?
Maybe when live. Today: self-host. Prices on /pricing; Cloud not live.
Partial SDK compat?
Yes. Exceptions via official Sentry SDKs. No replay, APM, or profiling as Epure features.