9 Commits

Include renames

Author	SHA1	Message	Date
autonomic-bot	161fe5e4d6	fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element	2026-07-13 23:58:20 +00:00
notplantsandnotplants	13458fac56	refactor: extract backup/restore into config scripts, trim comments ... Move the postgres and clickhouse backup/restore hook logic out of inline compose labels into dedicated pg_backup.sh / clickhouse_backup.sh config scripts (the pattern other recipes use), and trim the verbose explanatory comments down to the essential rationale, now living in the scripts.	2026-06-10 16:55:20 +00:00
autonomic-bot	9f8bcbc9e3	fix: clickhouse-backup install must succeed loudly, never silently degrade ... 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
autonomic-bot	b90a8c4239	fix: clickhouse entrypoint - backup download is best-effort (server must start regardless) ... 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
notplants	50a3715caa	chore: upgrade to 3.1.0+v2.0.0 ... 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
3wordchant	6c73753dc3	Add x86_64 support	2023-11-09 20:27:10 +00:00
p4u1	b72203b089	add backup labels for postgres and clickhouse	2023-11-09 11:17:45 +01:00
3wordchant	ee337feaea	Custom postgres entrypoint to handle major upgrades.. ... ..appropriated from the coop-cloud/outline recipe.	2023-08-11 12:15:23 +02:00
C Ræv	cc48f7761c	Initial import	2021-09-28 00:55:27 +02:00