engram `cloud serve` only registers /health, /sync/* and /dashboard/*;
Go's ServeMux answers "404 page not found" at the root path, which is
indistinguishable from a Traefik router miss. The deploy itself was fine
(both containers healthy), but the default domain pointed at `/` and
kept returning 404. Adding `path = "/dashboard"` routes the app's real
browser surface (login page / dashboard).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The template helper's ${password:N} can emit URL-reserved characters
(!@#$%^&*), which corrupt ENGRAM_DATABASE_URL while Postgres receives
the raw password, causing intermittent connection failures on first
deploy. Postgres is not exposed (internal network only), so a static
internal password is safe and matches the convention used by the
umami and documenso templates. Real secrets (JWT, cloud token, admin
token) remain randomly generated.
Engram Cloud is a self-hosted persistent-memory sync server for AI
coding agents. Deploys the published ghcr.io/gentleman-programming/engram
image with a PostgreSQL backend, auto-generated auth secrets (cloud
token, admin token, JWT secret), and a domain on the dashboard/API port.
