.dasho

written 2026-02-27 | updated 2026-02-28

4 min read

Git Servers

I have so many git servers, I might as well write about them.

soft-serve -> ssh git.4-0-4.io

Soft-serve is a self-hosted git server written in Go. It’s designed to be simple, fast, and easy to use. It has a nice tui interface for managing repositories and users, and it supports SSH and HTTP(S) access. I use it for my 404 project and it works great. You can see my soft-serve instance at:

ssh git.4-0-4.io

forgejo -> git-dev.4-0-4.io

Forgejo is a self-hosted git server written in Go. It’s a fork of Gitea, which is a fork of GitLab. It has a web interface for managing repositories and users, and it supports SSH and HTTP(S) access. I use it for my personal projects and it works well. You can see my forgejo instance at git-dev.4-0-4.io. I was going to use it more but turns out I much prefer the minimal stuff.

gitless

This is my own custom git server that builds static HTML pages for each repository. It’s designed to be simple, and only supports HTTP access. I use it for my personal projects and it works well. You can see my gitless instance at git.dasho.dev. It’s very minimal and just serves static pages, but it’s nice to have a simple way to share repositories without needing to set up a full git server. It is loosely based off the fantastic (stagit)https://git.codemadness.org/stagit/ but I wanted something that was more customizable and that I could easily integrate into my existing workflow, so I added markdown rendering of the README and some nice directory listing features and syntax highlighting and non-selectable line numbers and stuff all so that it just renders a little more useful than the default stagit setup is. Also because it’s static, I host it on Keybase Pages (just like this site) which makes hosting it super easy and free, and also makes it so that I don’t have to worry about security or anything since it’s just static files (and yes, you can still git clone from it)!

GitHub -> github.com/d-a-s-h-o

Even though Mircrosoft is the devil, I still use GitHub as a general source of truth. It’s a household name at this point, and it has a lot of nice features that I use, such as GitHub Actions for CI/CD, and GitHub Pages for hosting some of my projects. I also use it for open source projects that I want to share with the world, since it’s a popular platform and makes it easy for people to find and contribute to my projects. You can see my GitHub profile at github.com/d-a-s-h-o.

OTHER HONORABLE MENTIONS - but I don’t use them:

gitolite

Gitolite is a self-hosted git server written in Perl. It’s designed to be simple, fast, and easy to use. It has a command-line interface for managing repositories and users, and it supports SSH access. I don’t use it.

gogs

Gogs is a self-hosted git server written in Go. It’s designed to be simple, fast, and easy to use. It has a web interface for managing repositories and users, and it supports SSH and HTTP(S) access. I don’t use it.

gitlab

GitLab is a self-hosted git server written in Ruby. It’s designed to be a complete DevOps platform, with features such as issue tracking, CI/CD, and more. It has a web interface for managing repositories and users, and it supports SSH and HTTP(S) access. I don’t use it because it’s a bit too heavy for my needs, and I prefer to use more lightweight tools that I can easily integrate into my existing workflow.

gitea

Gitea is a self-hosted git server written in Go. It’s designed to be simple, fast, and easy to use. It has a web interface for managing repositories and users, and it supports SSH and HTTP(S) access. I don’t use it because I prefer forgejo, which is a fork of gitea that has some additional features and improvements that I like. Plus, forgejo has a more active development community and is more up-to-date with the latest features and security patches, so I prefer to use it over gitea.

sourcehut

Sourcehut is a self-hosted git server written in Go. It’s a bit more niche than the other git servers.

Bitbucket

Bitbucket is a git server owned by Atlassian… so yeah, I don’t use it.

When I inevitably get bored of all these and decide to switch to something else, I’ll probably update this page with the new git server that I use. But for now, these are the git servers that I use and recommend.