6 Commits

Include renames

Author	SHA1	Message	Date
cc-ci	9e7316499c	fix: keep config object versions in abra.sh only, not .env.sample ... 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	161fe5e4d6	fix: bump CLICKHOUSE_USER_CONF_VERSION v2→v3 for <clickhouse> root element	2026-07-13 23:58:20 +00:00
trav	ad6b93a1f4	fix: update .env.sample for CE v3.x SMTP requirements and add config versions	2026-06-24 17:37:04 +01:00
3wordchant	276f4f6933	Remove admin user stuff.. ... ..it's done on first launch now	2023-08-11 12:15:23 +02:00
javielico	ae8625df25	Adding two new variables to compose.yml to disable registration and login	2022-11-11 12:38:52 +00:00
C Ræv	cc48f7761c	Initial import	2021-09-28 00:55:27 +02:00