Just yesterday gitlab was down. Github has network issues on a pretty regular basis. Imagine not being able to push an update to your product because some 3rd party service is down. No thanks! We’ll set up our own git server. Shouldn’t be difficult.
Our general philosophy is to do as much as possible ourselves, for 3 mains reasons. One, we learn a bunch and this will help us troubleshoot when something goes wrong down the road. Two, we enjoy not being dependent on 3rd parties. Three, having your own stuff that never breaks with APIs that never change makes life way better. Yes, sometimes we reinvent the wheel, but that’s alright.
We’re two people and we build small scale apps (couple million users max). This means we don’t need much in terms of infrastructure. We don’t need even 5% of the functionality github has to offer. When we have specific needs we can often duck-tape a handful of Linux command line utilities together. In that spirit we’re setting up our own git server.
Goals: (a) create new repositories easily. (b) push/pull from VSCode. (c) push/pull to release server. (d) email hook on push.
I’m just going to follow the guide on git-scm.com. I’ll create a user called ‘git’ on our server, and set up public key authentication, with blockers for port forwarding. We have a whitelist for ssh logins, so I’m also updating
chsh I’m removing shell access for the git user as well.
If you lock everything down as aggressively as possible then you’re never one configuration file typo away from disaster. We have a firewall that whitelists IPs, a secondary firewall on a switch in the data center, we block users in sshd, disallow password authentication, we disable shells, we use fail2ban to ban/alert on suspicious activity, all sorts of monitoring and we probably have additional security measures I can’t think of right now. We’re big believers in this kind of layered security and I’m sure it will be the subject of future posts.
Now I’m going to deviate a little bit from the git-scm instructions. One, I want to rename the main branch to ‘main’. We can do that with
git symbolic-ref HEAD refs/heads/main. Future versions of git will make renaming the main branch easier, but this works.
I’ll also add a simple ‘post-receive’ hook so when any commits are pushed to the git server it’s posted to our wiki and we’ll get a nice email about it.
Basic bash script gets the job done. This is not a robust script that is intended to stand the test of time. We think of it as a type of interactive documentation. When we want to create a new git repository a year or two from now and we forget the steps we can just read the script, ask ourselves if it still looks reasonable and then run it.
It’s a good habit to sanity check your inputs, even on throwaway scripts. It’s easy to shoot yourself in the foot with bash shell expansion, after all.
#!/usr/bin/bash # usage: ./make-repo myrepo # # for git commands see # https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server # http://redsymbol.net/articles/unofficial-bash-strict-mode/ set -euo pipefail IFS=$'\n\t' if [[ "$1" =~ [^a-zA-Z0-9_-] ]]; then echo "use alphanum git repo name '$1' (exit)" exit fi sudo -u git mkdir /home/git/$1.git cd /home/git/$1.git sudo -u git git config --global init.defaultBranch main # only repo, not also a checkout sudo -u git git init --bare # debian git doesn't have rename head yet sudo -u git git symbolic-ref HEAD refs/heads/main # papyrs wiki hook sudo -u git ln -s /home/utils/git_receive_hook.py hooks/post-receive
Now it’s just a matter of adding the remote to my local git repository and we’re off to the races:
git remote add origin ssh://80daysgit:testproj
And I’ll add an entry to my ~/.ssh/config:
Host 80daysgit HostName [redacted] User git ForwardAgent yes IdentityFile ~/.ssh/80daysgit_id_rsa
That’s it. The remote shows up in VSCode automatically and I can push/pull with a click of a button.