mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-14 13:51:29 +01:00
dad16cd589
The current path of the `$GITEA_APP_INI` configuration file makes the forgejo application reset every time the container is restarted, unless a specific volume for this file is created. Consider the following: * This quirk is not documented * All configuration data resides in `/var/lib/gitea` * The custom configuration path defaults to `/var/lib/gitea/custom/conf` (see `forgejo -h`) * Containers mounting the volume `-v /foo/bar:/var/lib/gitea` already have this file available to modify. Another volume shouldn't be required * Containers using named volumes can use `docker cp` to modify the file inside the volume, if desired For these reasons, it makes more sense to use the default path for `$GITEA_APP_INI` rather than require users to create a dedicated volume for the file. Revert it back to its default while maintaining backwards compatibility (users can update by simply moving the file to the new path).
22 lines
690 B
Bash
Executable file
22 lines
690 B
Bash
Executable file
#!/bin/sh
|
|
|
|
# Protect against buggy runc in docker <20.10.6 causing problems in with Alpine >= 3.14
|
|
if [ ! -x /bin/sh ]; then
|
|
echo "Executable test for /bin/sh failed. Your Docker version is too old to run Alpine 3.14+ and Gitea. You must upgrade Docker.";
|
|
exit 1;
|
|
fi
|
|
|
|
if [ -x /usr/local/bin/docker-setup.sh ]; then
|
|
/usr/local/bin/docker-setup.sh || { echo 'docker setup failed' ; exit 1; }
|
|
fi
|
|
|
|
if [ $# -gt 0 ]; then
|
|
exec "$@"
|
|
else
|
|
# TODO: remove on next major version release
|
|
# Honour legacy config file if existing
|
|
if [ -f ${GITEA_APP_INI_LEGACY} ]; then
|
|
GITEA_APP_INI=${GITEA_APP_INI_LEGACY}
|
|
fi
|
|
exec /usr/local/bin/gitea -c ${GITEA_APP_INI} web
|
|
fi
|