Compare commits

..
Author SHA1 Message Date
autonomic-bot d41452663f fix(config): seed app.ini when missing OR empty (-s), bump v3
A release that mounted app.ini directly as a read-only swarm config leaves a 0-byte placeholder at
/etc/gitea/app.ini in the reattached config volume on upgrade; the original seed guard (! -f) treated
that as present and skipped, so Gitea booted the install wizard on an empty config (/api/v1/version
404). Guard on ! -s (missing OR empty) so the rendered config is seeded; bump DOCKER_SETUP_SH_VERSION
so the corrected entrypoint deploys (immutable swarm configs).
2026-06-18 02:52:50 +00:00
autonomic-bot 1a098452f4 fix(config): make app.ini writable so Gitea can persist secrets on (re)deploy
Gitea 1.24+ (re)generates and SAVES the [oauth2] JWT secret to /etc/gitea/app.ini 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 a warm reattach/redeploy, crash-looping the
container before any DB migration. Mount the rendered config at /etc/gitea/app.ini.init (read-only)
and seed it once into the writable config volume via docker-setup.sh, so Gitea owns a writable
/etc/gitea/app.ini. Bumps DOCKER_SETUP_SH_VERSION so the new entrypoint actually deploys.
2026-06-18 01:52:58 +00:00
notplants ce4de9e645 Merge pull request 'feat: support Git LFS on plain gitea' (#57) from lfs into master
Reviewed-on: https://git.coopcloud.tech/coop-cloud/gitea/pulls/57
Reviewed-by: ammaratef45 <ammaratef45@proton.me>
2026-06-15 21:08:52 +00:00
3 changed files with 16 additions and 2 deletions
+1 -1
View File
@@ -1,5 +1,5 @@
export APP_INI_VERSION=v22
export DOCKER_SETUP_SH_VERSION=v1
export DOCKER_SETUP_SH_VERSION=v3
export PG_BACKUP_VERSION=v1
abra_backup_app() {
+1 -1
View File
@@ -6,7 +6,7 @@ services:
image: "gitea/gitea:1.24.2-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
+14
View File
@@ -13,3 +13,17 @@ 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
# Seed app.ini into the WRITABLE config volume (/etc/gitea) from the read-only swarm config
# (mounted at /etc/gitea/app.ini.init). Gitea must be able to PERSIST settings to app.ini — e.g.
# 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
chmod 0600 /etc/gitea/app.ini 2>/dev/null || true