Infrastructure/forgejo
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-25 08:54:17 -05:00
Code Issues Activity
forgejo/docker
History
Gerard Salvatella dad16cd589 fix(Dockerfile.rootless): revert to default path for app.ini 
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).
2024-04-26 21:30:10 +02:00
..
root [BRANDING] container images: set APP_NAME 2024-02-05 16:02:13 +01:00
rootless fix(Dockerfile.rootless): revert to default path for app.ini 2024-04-26 21:30:10 +02:00
manifest.rootless.tmpl Do not publish docker release images on -dev tags (#25471) 2023-06-23 19:52:24 +00:00
manifest.tmpl Do not publish docker release images on -dev tags (#25471) 2023-06-23 19:52:24 +00:00
README.md [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2024-02-05 16:02:14 +01:00

README.md

Forgejo - Docker

The Dockerfile can be found in the root of repository. Dockerfile & Dockerfile.rootless.

The Docker image can be found on Codeberg.

Documentation on how you can use the docker image can be found on the Forgejo documentation website.