plausible

Author	SHA1	Message	Date
autonomic-bot	5c71affee1	chore: bump clickhouse to 23.4.6.25-alpine (23.4 LTS patch) cc-ci/testme cc-ci: success Details	2026-08-15 21:14:00 +00:00
cc-ci	9e7316499c	fix: keep config object versions in abra.sh only, not .env.sample cc-ci/testme cc-ci: success Details These five were added to .env.sample while abra.sh already exported them, so every deployment got a second, divergent copy. That is not just untidy. .env.sample becomes the operator .env at `abra app new`, and a .env is NEVER updated by a recipe upgrade. So the next time a recipe change bumps e.g. CLICKHOUSE_ENTRYPOINT_VERSION in abra.sh, an existing deployment keeps the stale value from its .env: the config CONTENT changes while the swarm config NAME does not, and swarm configs are immutable - FATA failed to update config <stack>_clickhouse_entrypoint_v6: only updates to Labels are allowed which is exactly the failure gitea hit with app_ini_v22. The fleet convention, consistent across gitea/discourse/keycloak/mailu: .env.sample carries SECRET_*_VERSION only (operator-managed secret rotation); config object versions live in abra.sh (recipe-managed - bumping one IS a recipe change). plausible main already followed this; only this branch diverged. abra.sh is unchanged and keeps CLICKHOUSE_USER_CONF_VERSION=v3 - that bump is correct, clickhouse-user-config.xml content genuinely changed.	2026-08-11 18:38:40 +00:00
autonomic-bot	867ebfafed	revert: restore sleep 10 (needed for pgautoupgrade window) cc-ci/testme cc-ci: success Details	2026-07-14 00:37:08 +00:00
autonomic-bot	b5cf2a9dd4	chore: drop sleep 10 from app command (align with upstream v3) cc-ci/testme cc-ci: failure Details	2026-07-14 00:24:10 +00:00
autonomic-bot	161fe5e4d6	fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element cc-ci/testme cc-ci: failure Details	2026-07-13 23:58:20 +00:00
trav	ad6b93a1f4	fix: update .env.sample for CE v3.x SMTP requirements and add config versions cc-ci/testme cc-ci: failure Details	2026-06-24 17:37:04 +01:00
trav	78124a5076	chore: upgrade to ghcr.io/plausible/community-edition:v3.2.1 - Switch app image from plausible/analytics:v2.0.0 to ghcr.io/plausible/community-edition:v3.2.1 (image registry changed at v3.x) - Bump ClickHouse from 23.4.2.11-alpine to 24.12-alpine (required for CE v3.x) - Add CLICKHOUSE_SKIP_USER_SETUP=1 env var to ClickHouse service (required for v3.0.0+) - Add ClickHouse healthcheck - Update clickhouse-user-config.xml: replace deprecated <yandex> root with <clickhouse> root; adopt CE low-resource profile settings for < 16 GB RAM hosts	2026-06-24 17:27:12 +01:00
notplants	657a540035	Merge pull request 'upgrade-3.1.0+v2.0.0' (#10 ) from upgrade-3.1.0+v2.0.0 into main Reviewed-on: https://git.coopcloud.tech/coop-cloud/plausible/pulls/10	2026-06-15 17:24:39 +00:00

1 changed files with 1 additions and 1 deletions

									
										compose.yml
									
		+1
		-1
	
												View File
												
					@@ -67,7 +67,7 @@ services:

					        backupbot.restore.post-hook: "/pg_backup.sh restore"

					        backupbot.restore.post-hook: "/pg_backup.sh restore"

					  plausible_events_db:

					  plausible_events_db:

					    image: clickhouse/clickhouse-server:23.4.2.11-alpine

					    image: clickhouse/clickhouse-server:23.4.6.25-alpine

					    volumes:

					    volumes:

					      - event-data:/var/lib/clickhouse

					      - event-data:/var/lib/clickhouse

					    entrypoint: /custom-entrypoint.sh

					    entrypoint: /custom-entrypoint.sh

Compare commits