Skip Navigation
32 comments
  • I mainly just use bare SSH and/or point my web server to my repos as I don't really need a whole UI for stuff I'm pretty much the only one that will ever use it.

    I feel like it's a git feature that's often overlook by those that have only used to GitHub/GitLab/Gitea before. Git was originally designed to just be a folder on a server you have SSH access (read-write) or HTTP(S) access (read-only).

    I've used Gogs and Gitea in the past but found it overkill for my needs.

    • Exactly what I do. Unless you need fancier collaboration features--issue tracker, UI for handling PRs, etc--a bare repo on the other side of ssh plus something like cgit if you want to make the code available via a browser is perfectly sufficient.

  • The only selfhosted github I know about is github enterprise.

    If you just want to host git repos, gitea, and gitlab are good. You don't need that to host git though, git is peer based and doesn't require a fancy dashboard to work.

  • I've had gitlab/gitlab-ce running on my NAS for 6+ months and it's been reliable, mostly as a central repository and off-device backup. It has CI/CD and other capabilities (gitlab/gitlab-runner, etc), but I've not implemented them.

  • I use stagit. It runs whenever I push code to a repo, and then serves everything as static HTML pages.

    It only provides a web interface for git repos though, and for the master branch.

  • https://gitolite.com/

    It's basic SSH-based git, but also allows you to manage permissions for users and groups based on their SSH keys. You do all configuration by editing a file in the adminstration repo and pushing those changes to the server. I don't want a web interface or any heavy service running all the time so this suits me perfectly.

32 comments