The first version of the "HOWTO upgrades, a guide for admins" is available 🚀 Make sure to read it before performing your next @gitea upgrade, what you will learn in a few minutes may save you hours of painful work ✨

forum.hostea.org/t/howto-gitea

---

Authored by @dachary

tip: when @Gitea is installed with docker, here is how you will want to run the doctor 🩺 to verify it is not sick 🤕

docker exec --user git gitea gitea doctor --all --log-file /tmp/doctor.log

Should there be a need for more information looking 👀 in the doctor.log will display the gory details:

docker exec --user git gitea cat /tmp/doctor.log

---

Authored by @dachary

A instance brought to the clinic was successfully upgraded from 1.11.0 to 1.16.8 🚀

A test run was conducted to identify potential issues and there was no surprise when upgrading the production instance.

It was also an opportunity to fix a minor bug in the Gitea doctor command and to improve the Hostea upgrade guide.

gitea.hostea.org/dachary/hoste

---

Authored by @dachary

tip: the gitea doctor command is available starting with 1.10.5 & 1.10.6 and for all versions >= 1.11.5.

But contrary to what one would expect it is not available for Gitea 1.11.0, 1.11.1, 1.11.2, 1.11.3, 1.11.4.

This was discovered today while migrating a Gitea 1.11.0 instance and the HOWTO Gitea upgrade was updated with this tip.

forum.hostea.org/t/howto-gitea

---

Authored by @dachary

zombies :zombie: first showed up in 2017 and they are now explained, the bug fix is tested and ready to be merged hostea.org/blog/zombies-part-2

@codeberg must collect more than a few on a daily basis ... when processes survive the timeout supposed to kill them.

---

Authored by @dachary

tip: make your app.ini file resistant 💪 to upcoming @Gitea 1.17 breaking changes related to where expects to find its data. It is simple ✨ make sure all path related variables (ending with PATH for the most part) are explicitly set with an absolute path for your current app.ini.

Use github.com/go-gitea/gitea/blob as a checklist.

If want to know more read the in depth analysis of a regression involving APP_DATA_PATH hostea.org/blog/path-not-found

---

Authored by @dachary

A regression introduced in 1.16.4 was identified today after a bug report from @codeberg.

Gitea users registered before the upgrade to 1.16.4 with an email that is no longer considered valid are unable to login or recover their account.

The simplest workaround is to kindly ask the Gitea admin to change the email: this is likely to only impact a handful of users, even on instances with thousands of registered accounts.

github.com/go-gitea/gitea/issu

---

Authored by @dachary

Hostea Gitea Hosting & Clinic's choices:

Mastodon

A newer server operated by the Mastodon gGmbH non-profit