Description
Description
According to the documentation, the path of the currently used configuration file can be queried by running the following command:
gitea --help
Application settings can be found in file
CustomConfwhich is by default,$GITEA_CUSTOM/conf/app.inibut may be different if your build has set this differently. Againgitea helpwill allow you review this variable and you can override it using the--configoption on thegiteabinary.
As I have observed, the configuration file on my instance is located in /etc/gitea/app.ini.
However, gitea --help shows a different path:
bash-5.1$ gitea --help
NAME:
Gitea - A painless self-hosted Git service
USAGE:
gitea [global options] command [command options] [arguments...]
VERSION:
v1.17.3 built with GNU Make 4.3, go1.18.7 : bindata, timetzdata, sqlite, sqlite_unlock_notify
[...]
DEFAULT CONFIGURATION:
CustomPath: /var/lib/gitea/custom (GITEA_CUSTOM)
CustomConf: /var/lib/gitea/custom/conf/app.ini
AppPath: /usr/local/bin/gitea
AppWorkPath: /var/lib/gitea
bash-5.1$
The /admin/config also shows the former as the config file:
The file indicated by gitea --help exists too, but possibly only because of an earlier misunderstanding of mine. About a year or 2 ago I had a hard time understanding where should I create the config file.
However, modifying this file does not seem to have an effect.
Gitea Version
v1.17.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Raspbian
How are you running Gitea?
In a self-built docker image built from the official Docker.rootless Dockerfile.
No source files or assets are modified, everything should be original.
Database
MySQL