diff --git a/README.md b/README.md index 8ec253b..37bb846 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,11 @@ This guide helps Gitea admins perform upgrades safely and provides guidance to troubleshoot problems. It covers [Gitea 1.2.0](https://github.com/go-gitea/gitea/releases/tag/v1.2.0) and above. -There are [many ways to install Gitea](https://docs.gitea.io/en-us/install-with-docker/) on various Operating Systems, each with their particular challenges and potential for trouble. The scope of this guide is limited to what [Hostea](https://hostea.org) uses daily: +There are [many ways to install Gitea](https://docs.gitea.io/en-us/install-with-docker/) on various Operating Systems, each with their particular challenges and potential for trouble. The scope of this guide is limited to what [Gna!](https://gna.org) uses daily: * Docker based installation (either [root](https://docs.gitea.io/en-us/install-with-docker/) or [rootless](https://docs.gitea.io/en-us/install-with-docker-rootless/)) using the [Gitea images published on the Docker hub](https://hub.docker.com/r/gitea/gitea). * Any GNU/Linux based Operating Systems -It is the source of truth that Hostea members use when maintaining the infrastructure and developing the service. +It is the source of truth that Gna! members use when maintaining the infrastructure and developing the service. #### Backup @@ -23,7 +23,7 @@ It is **critical** to verify that Gitea works very carefully. Restoring the back * Run `gitea doctor --all --log-file /tmp/doctor.log` and make sure it does not report any problem. The `gitea doctor` command is available for [Gitea 1.10.5](https://github.com/go-gitea/gitea/blob/v1.10.5/cmd/doctor.go), Gitea 1.10.6 and [Gitea >= 1.11.5](https://github.com/go-gitea/gitea/blob/v1.11.5/cmd/doctor.go). * Manually verify via the web interface. Making a checklist of a typical use case is a good way to not miss anything. -* If there is a problem of any kind, [increase the log level](https://docs.gitea.io/en-us/logging-configuration/#debugging-problems) and take a look at the logs. If you cannot figure out what the problem is, ask for help [in the Hostea forum](https://forum.hostea.org/c/clinic/5) before trying to fix it. +* If there is a problem of any kind, [increase the log level](https://docs.gitea.io/en-us/logging-configuration/#debugging-problems) and take a look at the logs. If you cannot figure out what the problem is, ask for help [in the Gna! forum](https://forum.gna.org/c/clinic/5) before trying to fix it. #### Gitea preparation @@ -81,7 +81,7 @@ The database version is stored in the database and can be retrieved with **selec ### When upgrading from a specific version... * Any version before [1.17](https://github.com/go-gitea/gitea/releases/tag/v1.17.2) - * preserve a custom gitconfig: [episode 1](https://hostea.org/blog/1-17-breaking-episode-1/), [episode 2](https://hostea.org/blog/1-17-breaking-episode-2/) + * preserve a custom gitconfig: [episode 1](https://gna.org/blog/1-17-breaking-episode-1/), [episode 2](https://gna.org/blog/1-17-breaking-episode-2/) * [1.13.0](https://blog.gitea.io/2020/12/gitea-1.13.0-is-released/) * The Webhook shared secret inside the webhook payload has been deprecated and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755 please use the secret header that uses an hmac signature to validate the webhook payload. * Git hooks now default to `off`! ([#13058](https://github.com/go-gitea/gitea/pull/13058)) @@ -112,7 +112,7 @@ In your config, you can check the [security](https://docs.gitea.io/en-us/config- ### Versions with known issues -Gogs from before September 2015 migrated to Gitea 1.17 may have a [dangling `pull_repo` table](https://forum.hostea.org/t/gitea-upgrade-from-gogs-to-1-16-8-unmigrated-pull-repo-table/73) and the corresponding pull requests will be removed by `gitea doctor --fix --all`. +Gogs from before September 2015 migrated to Gitea 1.17 may have a [dangling `pull_repo` table](https://forum.gna.org/t/gitea-upgrade-from-gogs-to-1-16-8-unmigrated-pull-repo-table/73) and the corresponding pull requests will be removed by `gitea doctor --fix --all`. [From the 1.11.3 release notes](https://blog.gitea.io/2020/03/gitea-1.11.3-and-1.10.6-released/): @@ -130,5 +130,5 @@ We remind users that a bug was discovered with `gitea dump` in 1.14.3–1.14.6 a * [Autoregistration via email not working](https://github.com/go-gitea/gitea/pull/19261) (introduced in [1.16.2](https://github.com/go-gitea/gitea/pull/18804) fixed in [1.16.6](https://github.com/go-gitea/gitea/pull/19312)) * `git push` fails after [git upgrades to v2.35.2](https://discourse.gitea.io/t/upgrading-git-push-fails-due-to-changed-security-policy-safe-directory/5185) or [Gitea docker image >= 1.16.6](https://discourse.gitea.io/t/upgrading-git-push-fails-due-to-changed-security-policy-safe-directory/5185) -* `app.example.ini` changed in a non backward compatible way [in Gitea 1.15 and up and causing path not found or permission denied](https://hostea.org/blog/path-not-found/). +* `app.example.ini` changed in a non backward compatible way [in Gitea 1.15 and up and causing path not found or permission denied](https://gna.org/blog/path-not-found/). * [unable to login into accounts](https://github.com/go-gitea/gitea/issues/19897) created with an email valid prior to 1.16.4 but [invalid for versions >=1.16.4](https://github.com/go-gitea/gitea/pull/19085). As of gitea >=1.17 `gitea doctor` [shows which emails are subject to this regression](https://github.com/go-gitea/gitea/pull/19903)