Commit Graph

31 Commits

Author SHA1 Message Date
9f8bcbc9e3 fix: clickhouse-backup install must succeed loudly, never silently degrade
Some checks failed
cc-ci/testme cc-ci: failure
Replaces the previous best-effort (|| true) approach: a deploy without
clickhouse-backup would have silently broken backup/restore, so the
entrypoint now hard-fails (visibly, in service logs) if the tool truly
cannot be installed — but makes that case effectively unreachable:

- cache the VERIFIED binary on the persistent clickhouse volume, keyed
  by version: downloaded at most once per app; container restarts never
  re-fetch (kills the re-download amplification that turned a GitHub
  throttle into a permanent crash-loop)
- canonical Altinity release URL (project moved; old path is a redirect)
- bounded retries with backoff + wget read timeout (a stalled connection
  can no longer hang the deploy)
- verify the binary executes before trusting or caching it (catches
  truncated downloads and a corrupt cache)
- compose: fix app depends_on to the real service name
  (plausible_events_db) — docker compose config was failing on it, which
  disabled CI image prepull and pushed pulls into the deploy window
- bump CLICKHOUSE_ENTRYPOINT_VERSION v4 -> v5 (swarm configs immutable)

Verified on a dev deploy: fresh download path, cached-restart path,
clickhouse-backup create/list/delete, and /api/health all green.
2026-06-09 19:09:13 +00:00
b90a8c4239 fix: clickhouse entrypoint - backup download is best-effort (server must start regardless)
Some checks failed
cc-ci/testme cc-ci: failure
The previous entrypoint treated clickhouse-backup as required: a download failure
(rate-limit or transient network) caused install_clickhouse_backup to return 1 which
with set -e exited the entrypoint before /entrypoint.sh ran. ClickHouse never started,
the swarm restarted it, the download was retried, amplifying the throttle -> crash-loop
-> deploy timeout (cc-ci Q4.7b).

Fix: install_clickhouse_backup || true — the server starts even if the backup tool
cannot be fetched. Backup/restore degrades until a later restart fetches it.

Also: fix stray trailing quote in backupbot.restore.post-hook; bump
CLICKHOUSE_ENTRYPOINT_VERSION v3->v4 (config content changed).
2026-06-09 18:30:18 +00:00
50a3715caa chore: upgrade to 3.1.0+v2.0.0
Some checks failed
cc-ci/testme cc-ci: failure
Minor bump — no operator action required (Postgres/ClickHouse changes are automatic).

- Postgres: use pgautoupgrade/pgautoupgrade:18-alpine in place of the custom
  pg_upgrade entrypoint. The existing cluster is upgraded in place automatically
  on deploy; PGDATA pinned to the legacy path; adds a pg_isready healthcheck.
  Removes entrypoint.postgres.sh.tmpl and DB_ENTRYPOINT_VERSION.
- ClickHouse backup fetch: cache the clickhouse-backup binary on the persistent
  volume and retry with backoff to avoid the download crash-loop. The tool is
  required — if it can't be installed after retries the entrypoint aborts and
  the server does not start, rather than coming up without backup/restore.
- Add CLICKHOUSE_DATABASE_URL; bump the clickhouse entrypoint config version.
- Remove a stray broken link reference in the README.
2026-06-09 15:46:28 +00:00
da159375d8 Update .drone.yml 2025-01-08 10:09:13 -08:00
f83774500d Remove swapfile 2024-05-03 09:10:11 +00:00
71dfab1129 Merge pull request 'fix backup and restore when database was already created' (#5) from p4u1/plausible:fix-backup-restore into main
Reviewed-on: https://git.coopcloud.tech/coop-cloud/plausible/pulls/5
2024-04-06 18:08:54 +00:00
2330e73915 SMTP settings incl now 2024-03-05 10:45:49 -05:00
bdc6e77e40 fix backup and restore 2023-11-11 13:18:40 +01:00
3wc
b26d957cad Add scary release note warning 2023-11-09 20:35:00 +00:00
3wc
4a70aadfb4 chore: publish 3.0.1+v2.0.0 release 3.0.1+v2.0.0 2023-11-09 20:31:44 +00:00
3wc
6c73753dc3 Add x86_64 support 2023-11-09 20:27:10 +00:00
3wc
1a29f24eba chore: publish 3.0.0+v2.0.0 release 3.0.0+v2.0.0 2023-11-09 19:20:28 +00:00
a30993cdb1 Merge pull request 'add backup labels for postgres and clickhouse' (#4) from p4u1/plausible:backup into main
Reviewed-on: https://git.coopcloud.tech/coop-cloud/plausible/pulls/4
2023-11-09 19:18:58 +00:00
b72203b089 add backup labels for postgres and clickhouse 2023-11-09 11:17:45 +01:00
3wc
7fa53d58eb Rename release note to make it actually work 2023-08-11 12:26:19 +02:00
3wc
c5b29affd8 chore: publish 2.0.0+v1.5.1 release 2.0.0+v1.5.1 2023-08-11 12:15:40 +02:00
3wc
ee337feaea Custom postgres entrypoint to handle major upgrades..
..appropriated from the coop-cloud/outline recipe.
2023-08-11 12:15:23 +02:00
3wc
276f4f6933 Remove admin user stuff..
..it's done on first launch now
2023-08-11 12:15:23 +02:00
3wc
f5f1bdd5eb Remove deprecated init-admin from startup command 2023-08-11 12:15:23 +02:00
fa5e91fc33 Changes to clickhouse logger 2023-08-11 12:15:23 +02:00
013352258b Readme update 2023-08-11 12:15:23 +02:00
3wc
d61a6c0bba Change version to 1.1.0 1.1.0+v1.5.1 2023-08-11 12:15:23 +02:00
c53bf21e35 Changed version of Plausible from latest to actual version, upgraded PoSQL and change clickhouse to actual docker image not Yandex 2023-08-11 12:15:13 +02:00
3wc
c9227acce5 Switch to self-hosted stack-ssh-deploy image [mass update] 2023-08-11 12:15:13 +02:00
3wc
10b628f075 Fix CI by adding networks: [mass update] 2023-08-11 12:15:13 +02:00
3wc
a94abcb823 Automatically generate catalogue on release [mass update]
Re: coop-cloud/recipes-catalogue-json#4
2023-08-11 12:15:13 +02:00
3wc
f0820ed7b8 Update abra syntax in examples (finally) [mass update] 2023-08-11 12:15:13 +02:00
ae8625df25 Adding two new variables to compose.yml to disable registration and login 2022-11-11 12:38:52 +00:00
3wc
e00f65d316 Goodbye, emojis! 😢
[ci skip]
2021-11-23 12:19:05 +02:00
3wc
1511ed624b Mass README update
[ci skip]
2021-11-21 21:23:35 +02:00
cc48f7761c Initial import 2021-09-28 00:55:27 +02:00