My Self-Hosted Setup: Two Boxes, One Repo and an AI Co-Admin
There are a hundred “what I self-host” posts out there, and most of them are a list of apps. Mine runs a lot of the same apps, so the list isn’t the interesting part. What’s different is how it’s put together and how it’s run:
- Two machines with different jobs. A cloud droplet for everything public, a mini PC at home for everything private.
- Nothing at home is reachable from the internet. Not even Jellyfin. No port forwards at all.
- The whole setup lives in one git repo, and I run it day to day with Claude Code as a co-admin, with guardrails.
Using a Self-Hosted Git Repository as a Maven Repository
If you maintain shared libraries across multiple Android or Kotlin Multiplatform projects, you’ve probably considered publishing them to a Maven repository. Maven Central works, but the publishing process is heavy — GPG signing, Sonatype staging, approval delays. For private or small-scale libraries, that’s overkill. If you already self-host a Git server like Gitea or Gogs, you can use it as a Maven repository with zero additional infrastructure.