Gna! is a Clinic to get help when a Forgejo instance throws errors after an upgrade and the admin is not sure how to troubleshoot the problem. It opened in May 2022 and welcomes new patients. It will also provide dedicated Forgejo hosting, including CI and more: subscribe to the blog or the Mastodon account to keep up to date.
[security] Gitea < 1.17.2 bypassing URL restrictions during migration explained
Prior to Gitea 1.17.2 a malicious Gitea server could be used to request local files using the migration web interface or the REST API.
[security] Gitea < 1.17.3 git option injection explained
Prior to Gitea 1.17.3 the web interface that displays the commit graph could be used to inject git options used by the Gitea server.
1.17 breaking changes episode 2: preserving a custom gitconfig
The location of the gitconfig file used by Gitea moved twice, here is a guide to sort out why and how to deal with it.
Get a Gitea instance with CI at Gna!
It is now possible to rent a Gitea instance by the month, with Woodpecker CI. A self-hostable hosting solution supported by a horizontal collective of individuals and organizations. 25% of the income is dedicated to help the Free Software projects it depends on such as Gitea, Enough, Django, etc.
1.17 breaking changes episode 1: preserving a custom gitconfig
The location of the gitconfig file used by Gitea moved and custom modifications must be manually moved as well.
[tutorial] A gentle introduction to the gitea doctor
The doctor command is useful to check the health of a running Gitea instance. Specially after performing an upgrade.
[solved] Zombies created by Gitea
Gitea can use process groups to kill its children using a negative PID to never create zombies.
[diagnostic] Zombies created by Gitea
An increasing number of zombies processes are created by Gitea because it only kills its direct children on timeout.
[solved] Gitea 1.15 and up: path not found or permission denied
After migrating from 1.15 or earlier to gitea 1.16 paths are no longer found and files cannot be created because of permission problems because the default example.ini file changed.
[solved] Gitea 1.16. error: fatal: unsafe repository is owned by someone else
If Gitea runs as user git, calls a patched Git version and a parent directory of the git repositories is owned by a user other than git, it will fail.
[solved] blank or error 500 page after login
After going to production, some Gitea users saw a blank page after login and had to manually type the URL of the project they wanted to see in the browser.
Introducing Hostea, a project Loïc Dachary and Aravinth Manivannan are working on to create a 100% Free software development suite, complete with CI/CD, static pages and gists
Project plans for a hosted Gitea online service
When an organization asks me about Gitea, I would like to direct them to a provider where they can rent an instance and just use it