Show newer

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

is committed to provide federated hosting to the general public as soon as it is available. Hostea will allow you to spawn a dedicated federated @Gitea instance provided by @forgefriends or when an alpha version is published :rocket:

Follow @hostea and help make it happen :sparkles:

---

Authored by @dachary

🚀 I now have clarity on how @gitea interprets the paths from the configuration file. I'd like to share that knowledge but how ... any ideas? 🤔

For instance AppWorkPath is never set in app.ini: it comes from either the --work-path argument, or the GITEA_WORK_DIR environment variable or defaults to the directory containing the Gitea binary.

Or gitea --help will display AppWorkPath as modified by GITEA_WORK_DIR but not when modified by --work-path.

---

Toot authored by @dachary

@ticoombs would you be interested to join the Gitea sysadmin discussion in the Hostea matrix room?

matrix.to/#/#hostea:matrix.bat

---

Toot authored by @dachary

Hostea Gitea Hosting & Clinic's choices:

Mastodon

A newer server operated by the Mastodon gGmbH non-profit