SSH keys are a very convenient and secure way to authenticate with Git servers such as GitHub. I used to use a single SSH key for the few private repositories I had, but in the meantime I have accumulated quite a number of SSH keys. Having different SSH keys for different purposes (e.g. personal keys and keys used for client work) makes it simpler for me to organize and rotate keys.

Containerization simplifies IT operations and nearly all standard software can be deployed in a container environment. Until today, I have operated GitLab as an omnibus installation. While Omnibus already greatly simplifies the deployment experience, there still needs to be done and configured a lot to run GitLab. Before GitLab supported Let’s Encrypt that even meant taking care of certificate renewal and making sure certificate configurations don’t break during upgrades. As I intend to run more software on the server running GitLab, I wanted to setup a reverse proxy that distributes traffic accordingly.