Selfhosted git - becoming more and more necessary since we all now have a team of agents generating code, data, and other text-based artifacts that need to be managed.

I also use Forgejo as a general automation platform via the Actions and runners. Scraping personal data, building websites, running random #python scripts on a schedule, updating my Vikunja projects - all easily doable and auditable.

Resources

• Forgejo – Beyond coding. We forge.
• How To: Setup and configure Forgejo with Actions - very complete guide, pretty much followed this to the letter
• Authelia Forgejo Docs
• Migrating Forgejo from SQLite to PostgreSQL | Sven’s blog - future database upgrade

Actions

• workflow-dispatch - trigger any Forgejo workflow from anywhere

Runners

I set up my Runner stack in a different VM so it can burn CPU aggressively on my secondary host. They are all runs-on: docker except one, which needed access to the host Docker sock in order to build Docker containers.

• To get a token that can be used by anyone/any org go to:
  • Admin -> Actions -> Runners
  • swap the command: in the docker config

Themes

• Interface customization | Forgejo
• catppuccin/gitea
• gitea-themes - gruvbox, catpucino, other common ones
• Evergarden for Gitea