Self-hosting my own GitLab instead of GitHub.

The author moved private projects off GitHub and now runs a self-hosted GitLab server at home to keep encryption keys and physical access under their control.

The author explains why they stopped using GitHub for certain projects and now self-host a GitLab instance at home. They say GitHub remains useful for public and large open-source work, but they wanted stronger personal control over truly private code. Hosting GitLab locally gives them sole custody of encryption keys and physical access. The piece contrasts convenience on large platforms with the desire for tighter control in a homelab setup. Key points: - The author has used GitHub for many years and values it for public and open-source repositories. - GitHub began offering free private repositories in 2019, but private projects are only as private as an account and the platform's policies allow. - Code uploaded to GitHub is protected in transit by TLS but is not subject to additional client-side encryption; the article reports that GitHub and its parent company Microsoft could technically access stored code. - The author now runs a self-hosted GitLab server at home and says they control encryption keys, physical access, and network exposure. - The author still uses GitHub for public sharing but keeps sensitive projects on the private home server. Summary: The move shifted custody of sensitive source code from a large hosted platform to a private, self-managed GitLab instance, emphasizing personal control over keys and access. Undetermined at this time.