redfix gitea fix v2 (-s seed, v3)

2026-06-18 02:52:52 +00:00
1 changed files with 9 additions and 3 deletions
@@ -14,9 +14,15 @@ mkdir -p ${GITEA_CUSTOM} && chmod 0500 ${GITEA_CUSTOM}
 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
+# Seed app.ini into the WRITABLE config volume (/etc/gitea) from the read-only swarm config
-# mounted directly as a read-only swarm config. So mount the rendered config as app.ini.init and seed
+# (mounted at /etc/gitea/app.ini.init). Gitea must be able to PERSIST settings to app.ini — e.g.
-# a writable copy. Use `! -s` (empty), not `! -f`: old direct-mount upgrades leave a 0-byte app.ini.
+# Gitea 1.24+ (re)generates and SAVES the [oauth2] JWT_SECRET at LoadCommonSettings; with app.ini
 # mounted directly as a read-only swarm config this fails fatally ("open /etc/gitea/app.ini:
 # read-only file system") on (re)deploy. Seed when MISSING OR EMPTY (`! -s`, not `! -f`): upgrading
 # from a release that mounted app.ini directly as a swarm config leaves a 0-byte placeholder at
 # /etc/gitea/app.ini in the reattached config volume — `! -f` would treat that as "present" and skip,
 # leaving Gitea to boot the install wizard on an empty config. A non-empty app.ini (Gitea's persisted
 # state) is preserved across restarts; truncate/delete it to force a re-seed from the rendered config.
 if [ ! -s /etc/gitea/app.ini ]; then
  cp /etc/gitea/app.ini.init /etc/gitea/app.ini
 fi