Previous upgrades were done using this script. This time around the idea is to also:
Run gitea doctor --all before the upgrade to spot outstanding problems
Run a filesystem backup before the upgrade (in case gitea dump does not produce a backup that can be restored)
Run gitea doctor --all after the upgrade
Perform manual verifications
I'll assist Raphaël in upgrading a Gitea instance running 1.16.5 to 1.16.8.
The upgrade was notified by a monitor probe (nagios?) based on the content of https://dl.gitea.io/gitea/version.json. It was noted on that occasion that it has 1.16.7 instead of the latest version. It is [apparently manually updated](https://matrix.to/#/!bXIgKPtRdSXHBnVBaz:osgeo.org/$wuvLU5yXfFX2HtYk_BN6RAq0CVCkf5F7h1U23GJDmRQ?via=libera.chat&via=t2bot.io&via=matrix.org) and sometime overlooked.
Previous upgrades were done using [this script](https://github.com/go-gitea/gitea/blob/ad551bffc1768245db075aa3d1b998b6f5997ae4/contrib/upgrade.sh). This time around the idea is to also:
* Run `gitea doctor --all` before the upgrade to spot outstanding problems
* Run a filesystem backup before the upgrade (in case `gitea dump` does not produce a backup that can be restored)
* Run `gitea doctor --all` after the upgrade
* Perform manual verifications
gitea --work-path /var/lib/gitea doctor -c /etc/gitea/app.ini --all
manual check of the web interface looks good
- [x] backup the postgres databases using a custom command
- [x] [upgrade.sh](https://github.com/go-gitea/gitea/blob/ad551bffc1768245db075aa3d1b998b6f5997ae4/contrib/upgrade.sh) -v 1.16.8
- [x] gitea --work-path /var/lib/gitea doctor -c /etc/gitea/app.ini --all
- [x] manual check of the web interface looks good
The script took a very long time (5 minutes?) to get to the PGP key servers and it looked like it was stuck downloading the binary
gitea doctor complained for not being able to write in /usr/local/bin/data/gitea because the --work-path was not set
* The script took a very long time (5 minutes?) to get to the PGP key servers and it looked like it was stuck downloading the binary
* gitea doctor complained for not being able to write in /usr/local/bin/data/gitea because the --work-path was not set
I'll assist Raphaël in upgrading a Gitea instance running 1.16.5 to 1.16.8.
The upgrade was notified by a monitor probe (nagios?) based on the content of https://dl.gitea.io/gitea/version.json. It was noted on that occasion that it has 1.16.7 instead of the latest version. It is apparently manually updated and sometime overlooked.
Previous upgrades were done using this script. This time around the idea is to also:
gitea doctor --all
before the upgrade to spot outstanding problemsgitea dump
does not produce a backup that can be restored)gitea doctor --all
after the upgrade