-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Add contrib/upgrade.sh
#18286
Add contrib/upgrade.sh
#18286
Conversation
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 can see how this is helpful for servers to fast upgrade their gitea instance. But the script needs some work to do, in order to avoid some issues.
I can accept this in |
Codecov Report
@@ Coverage Diff @@
## main #18286 +/- ##
=======================================
Coverage ? 46.03%
=======================================
Files ? 838
Lines ? 92725
Branches ? 0
=======================================
Hits ? 42689
Misses ? 43251
Partials ? 6785 Continue to review full report at Codecov.
|
Co-authored-by: delvh <[email protected]>
Co-authored-by: Gusted <[email protected]>
Co-authored-by: Gusted <[email protected]>
Hi @noerw, just a quick message to send you https://gist.github.com/HorlogeSkynet/d676b9204869842933169dbe35ed8650 (a personal script I maintain publicly for this purpose). |
🤖 wake up |
* giteaofficial/main: (28 commits) Added auto-save whitespace behavior if it changed manually (go-gitea#15566) Support custom ACME provider (go-gitea#18340) Refactor i18n, use Locale to provide i18n/translation related functions (go-gitea#18648) Only request write when necessary (go-gitea#18657) [skip ci] Updated translations via Crowdin Add separate SSH_USER config option (go-gitea#17584) Be more lenient with label colors (go-gitea#17752) remove redundant call to UpdateRepoStats during migration (go-gitea#18591) more repo dump/restore tests, including pull requests (go-gitea#18621) No longer show the db-downgrade SQL in production (go-gitea#18653) Fix the missing i18n key for update checker (go-gitea#18646) Update gitea-vet (go-gitea#18640) Future proof for 1.18 (go-gitea#18644) Add `contrib/upgrade.sh` (go-gitea#18286) If rendering has failed due to a net.OpError stop rendering (go-gitea#18642) Delete old git.NewCommand() and use it as git.NewCommandContext() (go-gitea#18552) Update JS dependencies (go-gitea#18636) fix commits_list_small.tmpl (go-gitea#18641) Fix `make fmt` and `make fmt-check` (go-gitea#18633) Frontport of changelog for v1.16.1 (go-gitea#18615) ...
Adds an upgrade script that automates upgrading installations on Linux from binary releases, so people don't need to reinvent the wheel. Hopefully this leads to less questions about how to upgrade, and consequently less Gitea instances running unmaintained versions in the wild. Co-authored-by: delvh <[email protected]> Co-authored-by: Gusted <[email protected]> Co-authored-by: zeripath <[email protected]> Co-authored-by: 6543 <[email protected]>
Adds an upgrade script that automates upgrading installations on Linux from binary releases, so people don't need to reinvent the wheel. Hopefully this leads to less questions about how to upgrade, and consequently less Gitea instances running unmaintained versions in the wild.
Feel free to suggest improvements.
originally posted in #17405 (comment)
edit: This is meant as a stopgap for common linux deployments, an updater supporting all the different ways gitea can be deployed probably has ~2 orders of magnitude more complexity, so I didn't even try to accomodate for that.
Even for differing linux environments I assumed the user screens/tests/adapts this script for their needs, but I'll implement your feedback to make it more portable later (though given the tradeoff between portability and readability/extensibility, I side more with the latter option).