Add documentation on how to update Gitea to new version #4500
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4500 +/- ##
======================================
Coverage 20.2% 20.2%
======================================
Files 156 156
Lines 31140 31140
======================================
Hits 6292 6292
Misses 23890 23890
Partials 958 958Continue to review full report at Codecov.
|
bkcsoft
added
the
lgtm/need 2
|
I think it should note to do backup and stop gitea before replacing binary |
lafriks
changed the title
| @@ -90,6 +90,20 @@ cp gitea /usr/local/bin/gitea | |||
|
|
|||
| See how to create [Linux service]({{< relref "run-as-service-in-ubuntu.en-us.md" >}}) | |||
|
|
|||
| ## Updating to a new version | |||
|
|
|||
| You can update to a new version of gitea by stopping gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance. | |||
There was a problem hiding this comment.
What if the gitea binary is at another location?
There was a problem hiding this comment.
@JonasFranzDEV installation from binary recommends this location so we should stick to this location
|
@bkroll please fix build error |
bkcsoft
added
lgtm/need 1
| binary. | ||
|
|
||
| To solve this, go to the admin options and run the task `Resynchronize pre-receive, | ||
| update and post-receive hooks of all repositories` to update all hooks to contain |
There was a problem hiding this comment.
Please add warning that if a user has custom Git hooks this will overwrite them (I know that the admin dashboard has it, but more warning is better).
Also, another debugging step would be to re-write the authorized key file, as it puts the path to the binary in that file and if the binary name changes then this will also have issues when pushing via SSH.
|
OK I'm off at this point. I just tried to contribute that piece of documentation on how to update in general, as #3817 was the only instruction on this that I could find. I'm afraid I can't deliver a more detailed documentation than I did so far, because of a lack of both Gitea experience and time. I have never used custom git hooks and I'm not sure what you would like to see written on the authorized key file (#4500 (review)), so someone else would need to chime in here. |
|
@bkroll I can add the documentation I requested. Is it ok if I modify your PR? |
|
Yes, sure @techknowlogick. Thanks! |
bkcsoft
added
lgtm/done
|
Thanks @bkroll 😄 |
Providing documentation for updating gitea, as asked in #3817