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.
16 lines
263 B
Bash
16 lines
263 B
Bash
export APP_INI_VERSION=v22
|
|
export DOCKER_SETUP_SH_VERSION=v2
|
|
export PG_BACKUP_VERSION=v1
|
|
|
|
abra_backup_app() {
|
|
_abra_backup_dir "app:/var/lib/gitea"
|
|
}
|
|
|
|
abra_backup_db() {
|
|
_abra_backup_mysql "db" "gitea"
|
|
}
|
|
|
|
abra_backup() {
|
|
abra_backup_app && abra_backup_db
|
|
}
|