Skip to content

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

Merged
merged 10 commits into from
Apr 30, 2020
4 changes: 4 additions & 0 deletions docs/content/doc/installation/from-binary.en-us.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,10 @@ It is recommended you do a [backup]({{< relref "doc/usage/backup-and-restore.en-
If you have carried out the installation steps as described above, the binary should
have the generic name `gitea`. Do not change this, i.e. to include the version number.

To restart your gitea instance, we recommand to use if you know your gitea PID ```kill -1 $GITEA_PID``` otherwise you can use ```killall -1 gitea``` or ```pkill -1 gitea```

Note : We don't recommand to use SIGKILL signal, you could broke some gitea behaviors as it will not gracefully stop (task in queue, indexers processes, ...)

See below for troubleshooting instructions to repair broken repositories after
an update of your Gitea version.

Expand Down