mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-12-22 12:54:53 -05: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).
6 lines
390 B
Markdown
6 lines
390 B
Markdown
Reverted the rootless container image path in `GITEA_APP_INI` from
|
|
`/etc/gitea/app.ini` to its default value of
|
|
`/var/lib/gitea/custom/conf/app.ini`. This allows container users to not have
|
|
to mount two separate volumes (one for the configuration data and one for the
|
|
configuration `.ini` file). A warning is issued for users with the legacy
|
|
configuration on how to update to the new path.
|