notplants
83605ff3fa
Gitea 1.24+ persists settings back to app.ini on boot (e.g. WORK_PATH). Mounting app.ini directly as a read-only swarm config makes that write fail (logged error, possible repo-access bugs). Mount the rendered config as app.ini.init and seed a writable copy in the config volume instead.
24 lines
1.0 KiB
Cheetah
24 lines
1.0 KiB
Cheetah
#!/bin/bash
|
|
|
|
# modified version of https://github.com/go-gitea/gitea/blob/d7dbe4feebac7805a4ca184f0989f58de8063d96/docker/rootless/usr/local/bin/docker-setup.sh
|
|
# also see https://github.com/go-gitea/gitea/pull/14762#issuecomment-829224656
|
|
|
|
# Prepare git folder
|
|
mkdir -p ${HOME} && chmod 0700 ${HOME}
|
|
if [ ! -w ${HOME} ]; then echo "${HOME} is not writable"; exit 1; fi
|
|
|
|
# Prepare custom folder
|
|
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
|
|
|
|
# Gitea 1.24+ writes settings back to app.ini on boot (e.g. WORK_PATH), which fails when app.ini is
|
|
# mounted directly as a read-only swarm config. So mount the rendered config as app.ini.init and seed
|
|
# a writable copy. Use `! -s` (empty), not `! -f`: old direct-mount upgrades leave a 0-byte app.ini.
|
|
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
|