Files
cc-ci-orchestrator/cc-ci-plan/upstream/plausible.md
2026-06-05 04:35:44 +00:00

1.6 KiB

Upstream sources — plausible

service image source repo releases / changelog
app plausible/analytics (old) / ghcr.io/plausible/community-edition (new) https://github.com/plausible/analytics https://github.com/plausible/analytics/releases
db postgres https://github.com/postgres/postgres https://www.postgresql.org/docs/release/
plausible_events_db clickhouse/clickhouse-server https://github.com/ClickHouse/ClickHouse https://github.com/ClickHouse/ClickHouse/blob/master/CHANGELOG.md

Standing notes

  • Plausible uses a custom entrypoint.postgres.sh.tmpl that auto-runs pg_upgrade --link on major version changes — single-step major upgrades are safe and automatic. Do NOT skip more than one major postgres version at a time (e.g. 13→14 is fine; 13→15 is two steps and risks data corruption).
  • The plausible app image moved from plausible/analytics on Docker Hub to ghcr.io/plausible/community-edition starting with v2.1.x. The v2.0.0 image is still on Docker Hub as plausible/analytics:v2.0.0.
  • ClickHouse version must be compatible with the plausible app version. Check release notes when upgrading either. The 23.4.2.11-alpine image works with plausible v2.0.0.
  • Recipe version label convention: <recipe-semver>+<app-version> (e.g. 3.0.1+v2.0.0).
  • For postgres major upgrades: bump DB_ENTRYPOINT_VERSION in abra.sh to force config re-deploy if entrypoint script changes. Current is v1 (handles 13→14 and beyond via pg_upgrade).
  • TOTP_VAULT_KEY env var was added in v2.1.x — not needed for v2.0.0.