-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Disable auto-migrate in docker container #5730
Disable auto-migrate in docker container #5730
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5730 +/- ##
=========================================
Coverage ? 37.76%
=========================================
Files ? 327
Lines ? 47803
Branches ? 0
=========================================
Hits ? 18052
Misses ? 27160
Partials ? 2591 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't match the line I suggested:
(cd /app/gitea; exec su-exec $USER /app/gitea/gitea migrate)
Your suggested working directory isn't correct.
The thing is we need try to replicate the exact environment that docker runs Gitea in so that relative paths in the conf file work. See https://github.com/go-gitea/gitea/blob/master/docker/etc/s6/gitea/run
@zeripath updated path |
OK I think this is worth a try. It's a shame we can't really test it... |
After using this PR migration is still not working:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should just remove it rather than comment it out but in either case disabling this seems appropriate.
But what was this used for? As far as I understand this is used to auto migrate for things like docker and using image :latest. |
There was a misunderstanding about why a user provided app.ini was not working. I think the issue actually might have been that the app.ini was not readable by Gitea. In any case this fix caused more problems than it should have |
Credit to @zeripath
Hopefully fixes #5688
ping @AragurDEV