← Back to context

Comment by mejutoco

18 hours ago

> 4. Do you just want to host repositories?

an ssh connection and

    git --bare init

on your ssh accessible server works just fine

“Just” is a four letter word and a trap our industry repeatedly falls into.

https://sgringwe.com/2019/10/10/Please-just-stop-saying-just

  • I hadn't read this article until now, but I started catching myself using the word at work a few years ago and I've actively been trying to avoid using it for the reasons laid out in this post.

  • If all you want to do is host repositories, “just” is the appropriate word here. For lone wolf work, all I care about is having a remote that mirrors all the changes and branches I create locally. It’s just redundancy. A git bare repo and SSH are all that’s needed.

    I don’t do pull requests to myself, and I don’t need a bug tracker or CI.

That's what gitolite does with some helper scripts for creating/setting up the repositories, adding metadata to the configs, etc. That way your `git` user can be set to reject ssh login attempts. The projects are managed by pushing a config to a gitolite admin repository.

  • Cool thing about gitolite is that you manage it using text files and committing to the gitolite admin git repository.

    We were using it until we grew tired of not having a web view to comment and review patches so we switched to gitea.

It is much more complex than this to get basic GitHub functionality anyone who has tried can tell you that. It feels like it should be a simple command but it absolutely isn’t