-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Propose an explanation how to restart gracefully gitea after an update #10866
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
Conversation
* new reading by @techknowlogick
* Add a note about a simple kill
Codecov Report
@@ Coverage Diff @@
## master #10866 +/- ##
==========================================
+ Coverage 43.40% 43.42% +0.02%
==========================================
Files 593 593
Lines 83271 83276 +5
==========================================
+ Hits 36140 36162 +22
+ Misses 42640 42623 -17
Partials 4491 4491
Continue to review full report at Codecov.
|
I'd think we should be 'recommending' using the service file since thats our previous recommendation in the same document
And manually killing as a last resort if not. |
There also:
|
Either of those seem much better to recommend than killall etc... I'm not familiar with it but should the systemd unit be trying to use gitea manager to restart/shutdown? Is that better? Or does it otherwise need to be updated for newer graceful features? |
Hello systemd is a solution among other sys init solution. And gitea help presume mono instance usage with defaults paths. I don't know if it's adapted when we use custom path. Maybe we could add a warning about our preferred solution and propose other sys init approach but is not related to this PR. In my personal use, as I've two instances and I don't understand well systemd, I've written a bash script as far as I understand. I think I'm not alone to launch gitea with a script it's why I propose this addon. |
@mrsdizzie systemd will natively use kill and kill -1 to stop or restart processes as standard. Gitea catches kill -1 and causes a graceful restart. It's actually fine to kill -1 a Gitea process, similarly kill. The only problem is kill -9 which can cause loss of data and corruption. |
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.
systemd
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.
As a side note, this page doesn't even mention Windows. We should change the title to "From binary (Unix-like)" and create a separate Windows page. 😓
Follow @guillep2k patch Co-Authored-By: guillep2k <[email protected]>
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.
Some suggestions for improvement.
* apply @zertrin correction
typo over typo :) Co-Authored-By: 6543 <[email protected]>
make lg-tm work |
go-gitea#10866) Co-authored-by: guillep2k <[email protected]> Co-authored-by: 6543 <[email protected]> Co-authored-by: Lauris BH <[email protected]>
This documentation patch propose to be more clear about kill action.
Gitea support
-1
signal to gracefully stop its actions.Thanks to @zeripath about his explanations