Compare commits

..
4 changed files with 4 additions and 18 deletions
+1 -1
View File
@@ -1,5 +1,5 @@
export APP_INI_VERSION=v22
export DOCKER_SETUP_SH_VERSION=v3
export DOCKER_SETUP_SH_VERSION=v1
export PG_BACKUP_VERSION=v1
abra_backup_app() {
+1 -1
View File
@@ -10,7 +10,7 @@ services:
secrets:
- db_password
db:
image: postgres:15.13
image: postgres:15.18
deploy:
labels:
backupbot.backup.pre-hook: "/pg_backup.sh backup"
+2 -2
View File
@@ -3,10 +3,10 @@ version: "3.8"
services:
app:
image: "gitea/gitea:1.24.2-rootless"
image: "gitea/gitea:1.26.2-rootless"
configs:
- source: app_ini
target: /etc/gitea/app.ini.init
target: /etc/gitea/app.ini
- source: docker_setup_sh
target: /usr/local/bin/docker-setup.sh
mode: 0555
-14
View File
@@ -13,17 +13,3 @@ 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