-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Rename gitea/conf/app.ini to app.ini.example #1432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Why is it confusing? It's even not shipped with the binary. |
@tboerger Many people compile from source. I actually liked the idea. Alternatively could be an "example" folder. |
As far as I know conf/app.ini is actually what gets compiled into bindata,
for builds with the `bindata` tag, and is otherwise read from FS before
the custom one for other builds.
If that's confirmed, I think it shouldn't be renamed.
Note that bindata builds should not even have a conf/ directory as the
binary would be enough to run.
|
Yes, that's what I thought but if I have understood it correctly all defaults are loaded from modules/setting/setting.go. Only reference that I can find is in gogs_migration.sh In Gogs it works like you have described it. |
Interesting, I confirm you can actually move away the conf/ directory
even with non-bindata build. I'm not sure renaming to .example but keeping
it in that dir helps anyone though, because dropping the .example part
would still have no effect unless it's moved to the custom dir.
|
Good point. Renaming the folder and explaining the purpose of the file might be a better idea. |
You have my 👍 on changing the name of the file/folder @tboerger We still have to consider people that don't install from binary 😉 |
Closed by #1522 |
The app.ini found in gitea/conf is not an active configuration file. To save the confusion it might be a good idea to rename it to app.ini.example.
The text was updated successfully, but these errors were encountered: