All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why I moved from GitHub to self-hosted Forgejo: Digital sovereignty over convenience

By

jorijn

18d ago· 17 min readenOpinion

Summary

The author explains their decision to migrate from GitHub to a self-hosted Forgejo instance, driven by concerns over digital sovereignty and platform ownership rather than reliability issues like outages. They detail the technical architecture of their hardened NUC setup and highlight that the Dutch government made a similar move, launching code.overheid.nl on a self-hosted Forgejo instance to legally own their source code. The article covers the philosophical and practical reasons for prioritizing control over one's code infrastructure.

Key quotes

· 3 pulled
The Dutch government just made the same call.
The platform was born from the requirement that the ministry has to legally publish [its] source code on a place that [it] owns.
Not because of the outages, but because of who owns what runs on top of them.
Snippet from the RSS feed
I left GitHub for self-hosted Forgejo on a hardened NUC. The reason is digital sovereignty, not reliability outages. Here's the thinking and the architecture.

You might also wanna read