Note: Gitea must perform a full restart to see configuration changes. Is set under the “Configuration” tab on the site administration page. GITEA_CUSTOM might, for example, be set by an init script. If the CustomPath folder can’t be found despite checking gitea help, check the GITEA_CUSTOMĮnvironment variable this can be used to override the default path to something else. $GITEA_CUSTOM/conf/app.ini but may be different if your build has set this differently.Īgain gitea help will allow you review this variable and you can override it using the Distributions may provide a symlink for custom using /etc/gitea/.Īpplication settings can be found in file CustomConf which is by default, Gitea will attempt to create required folders, includingĬustom/. If installed from a distribution, these paths will likely be modified to If Gitea is deployed from binary, all default paths will be relative to the Giteaīinary. Using the -custom-path option on the gitea binary. The CustomPath by setting either the GITEA_CUSTOM environment variable or by The path on the Configuration tab in the Site Administration page. You can check the CustomPath using gitea help. This is the central place to override configuration settings, The custom folder from the running directory, but may be different if your build has
Customizing Gitea is typically done using the CustomPath folder - by default this is
0 kommentar(er)
