fix: seed app.ini into writable config volume for Gitea 1.24+

Gitea 1.24+ persists settings back to app.ini on boot (e.g. WORK_PATH). Mounting app.ini directly as a read-only swarm config makes that write fail (logged error, possible repo-access bugs). Mount the rendered config as app.ini.init and seed a writable copy in the config volume instead.
chore: publish 3.6.3+1.27.1-rootless release
2026-08-11 16:49:26 +00:00 · 2026-08-10 12:57:05 -04:00 · 2026-08-10 16:54:41 +00:00 · 2026-08-10 16:52:09 +00:00 · 2026-08-10 12:32:49 -04:00 · 2026-08-10 16:32:05 +00:00
4 changed files with 12 additions and 4 deletions
@@ -1,5 +1,5 @@
-export APP_INI_VERSION=v22
-export DOCKER_SETUP_SH_VERSION=v1
+export APP_INI_VERSION=v23
+export DOCKER_SETUP_SH_VERSION=v3
 export PG_BACKUP_VERSION=v1

 abra_backup_app() {
@@ -6,7 +6,7 @@ services:
    image: "gitea/gitea:1.27.1-rootless"
    configs:
      - source: app_ini
-        target: /etc/gitea/app.ini
+        target: /etc/gitea/app.ini.init
      - source: docker_setup_sh
        target: /usr/local/bin/docker-setup.sh
        mode: 0555
@@ -87,7 +87,7 @@ services:
        - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}"
        - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolmaxage=100"
        - "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true"
-        - coop-cloud.${STACK_NAME}.version=3.6.0+1.24.2-rootless
+        - coop-cloud.${STACK_NAME}.version=3.6.3+1.27.1-rootless


 networks:
@@ -13,3 +13,11 @@ mkdir -p ${GITEA_CUSTOM} && chmod 0500 ${GITEA_CUSTOM}
 # Prepare temp folder
 mkdir -p ${GITEA_TEMP} && chmod 0700 ${GITEA_TEMP}
 if [ ! -w ${GITEA_TEMP} ]; then echo "${GITEA_TEMP} is not writable"; exit 1; fi
+
+# Gitea 1.24+ writes settings back to app.ini on boot (e.g. WORK_PATH), which fails when app.ini is
+# mounted directly as a read-only swarm config. So mount the rendered config as app.ini.init and seed
+# a writable copy. Use `! -s` (empty), not `! -f`: old direct-mount upgrades leave a 0-byte app.ini.
+if [ ! -s /etc/gitea/app.ini ]; then
+  cp /etc/gitea/app.ini.init /etc/gitea/app.ini
+fi
+chmod 0600 /etc/gitea/app.ini 2>/dev/null || true
Author	SHA1	Message	Date
notplants	d0243cf724	fix: seed app.ini into writable config volume for Gitea 1.24+ cc-ci/testme cc-ci: success Details Gitea 1.24+ persists settings back to app.ini on boot (e.g. WORK_PATH). Mounting app.ini directly as a read-only swarm config makes that write fail (logged error, possible repo-access bugs). Mount the rendered config as app.ini.init and seed a writable copy in the config volume instead.	2026-08-11 16:49:26 +00:00
notplants	97fe2bf213	chore: publish 3.6.3+1.27.1-rootless release	2026-08-10 12:57:05 -04:00
notplants	fe536b276b	Merge pull request 'fix: bump APP_INI_VERSION to v23' (#62 ) from fix-app-ini-version into master Reviewed-on: https://git.coopcloud.tech/coop-cloud/gitea/pulls/62	2026-08-10 16:54:41 +00:00
autonomic-bot	852717d212	fix: bump APP_INI_VERSION to v23 cc-ci/testme cc-ci: success Details app.ini.tmpl changed in "BREAKING CHANGE: remove forgejo" but the config version stayed at v22. Swarm configs are immutable, so upgrading an existing deployment aborts: FATA failed to update config <stack>_app_ini_v22: Error response from daemon: rpc error: code = InvalidArgument desc = only updates to Labels are allowed Bumping to v23 makes Swarm create a new config object instead of mutating v22; the orphaned v22 can be pruned after rollout.	2026-08-10 16:52:09 +00:00
notplants	1f987b4ab3	chore: publish 3.6.2+1.27.1-rootless release	2026-08-10 12:32:49 -04:00
notplants	a8d2231e74	Merge pull request 'chore: upgrade gitea to 1.27.1-rootless' (#61 ) from upgrade-7561bed into master Reviewed-on: https://git.coopcloud.tech/coop-cloud/gitea/pulls/61	2026-08-10 16:32:05 +00:00