coolify-bugsink

Bugsink (Postgres) as a Coolify Docker Compose resource.

Coolify ships a built-in Bugsink template, but it uses MySQL and an unpinned image. This is the upstream Postgres sample adapted to Coolify.

Deploy

1. Coolify → project → + New → Docker Compose → point at this repo.
2. Set BUGSINK_ADMIN_EMAIL. It is marked required, so it appears at the top of the environment list. Do this before the first deploy — see below.
3. Deploy. Coolify generates the domain and all secrets.
4. Log in with that email and the generated SERVICE_PASSWORD_ADMIN, visible under Environment Variables.

What Coolify fills in

Variable	Source
SERVICE_URL_BUGSINK_8000	Registers the domain and routes the proxy to port 8000
BASE_URL	SERVICE_URL_BUGSINK — the same URL, without the port
SECRET_KEY	SERVICE_PASSWORD_64_BUGSINK (64 chars; Bugsink requires at least 50)
SERVICE_USER_BUGSINK / SERVICE_PASSWORD_BUGSINK	Postgres credentials, shared by both services
SERVICE_PASSWORD_ADMIN	Initial superuser password

Yours to set

Variable	Default
BUGSINK_ADMIN_EMAIL	admin@example.org — required; first deploy only
POSTGRES_DB	bugsink — first deploy only

BEHIND_HTTPS_PROXY=true assumes you serve Bugsink over HTTPS, which is Coolify's default. Flip it if you don't.

First deploy only

BUGSINK_ADMIN_EMAIL, POSTGRES_DB, SERVICE_USER_BUGSINK, and SERVICE_PASSWORD_BUGSINK are consumed once, when the stack initialises. Bugsink creates the superuser only if none exists; Postgres reads its credentials only when it initialises an empty data directory. Editing any of them later in Coolify's UI changes what the web container sends without changing what the database expects, so the web container crash-loops on authentication while Postgres keeps reporting healthy.

Rotating secrets

To change the database password after deployment, change it in Postgres first:

# in Coolify's terminal for the db container
psql -U "$POSTGRES_USER" -d "$POSTGRES_DB" \
  -c "ALTER USER \"$POSTGRES_USER\" WITH PASSWORD 'new-password';"

Then update SERVICE_PASSWORD_BUGSINK in Coolify to match and redeploy.

To change the admin password, use Bugsink's own UI, or manage.py changepassword in the web container. Rotating SERVICE_PASSWORD_ADMIN in Coolify has no effect on an existing user.

Keep replacement secrets alphanumeric

Two secrets are parsed, not just passed: SERVICE_PASSWORD_BUGSINK goes into DATABASE_URL and SERVICE_PASSWORD_ADMIN is split on :. Coolify's SERVICE_PASSWORD_* generator is symbol-free, so the defaults are safe. If you replace either by hand, keep it alphanumeric — :, @, /, and # corrupt the value, and neither failure names the cause.

Sending events

Point a Sentry SDK at the DSN from Bugsink's UI. Any Sentry SDK works.

License

MIT — see LICENSE.