-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
[1.20.0] After update an new error about WORK_PATH are logged #25932
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
I think the log message is clear enough, right? Update: I see your point, see the comment below. |
The document PR is : Update path related documents #25417 , sorry for that it hasn't been merged yet. You can do |
No problem, thanks for the update. But in my case chmod will not be an option, because the app.ini is managed. So you go to the hell, when both (the app and the management system) write to the file. So when the PR will be merged, the dev docu will be updated and I can read it :) |
Thank you for the details. IMO it won't be a problem, because Gitea can update some necessary config options automatically, and it won't break anything even if the file is managed.
No need to wait :) In short: if you want to manage the app.ini by your tools, just put "WORK_PATH = /the/gitea/work-path" in your In history, Gitea's "work-path" is its binary directory. So the default directory layout is:
To avoid "guessing" the "work-path", now, the WORK_PATH option in "app.ini" is used to provide a stable work-path value. |
Ah the global block. I will try it at the evening today |
Yes, this will work. While the PR is on the road, it will close this here. |
Description
After the update this error is logged:
The text was updated successfully, but these errors were encountered: