chore: upgrade gitea to 1.26.2-rootless, postgres to 15.18

abra.sh

@@ -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() {

compose.yml

@@ -6,7 +6,7 @@ services:
     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

docker-setup.sh.tmpl

@@ -13,13 +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 app.ini.init). Gitea persists settings back to app.ini — e.g. it saves the
-# [oauth2] JWT_SECRET on boot since 1.24 — which crashes if app.ini is the read-only mount itself.
-# Test `! -s` (empty), not `! -f` (missing): upgrades from the old direct-mount layout leave a
-# 0-byte app.ini placeholder that still needs seeding. A non-empty app.ini is left untouched.
-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