Security-conscious readers may have picked up that we're only using insecure HTTP, which might be fine for local installs or air-gapped networks, but if you're running on a cloud server, want to protect your server from man-in-the-middle attacks, or just want to follow best practices, I've outlined two ways that you can implement HTTPS. The first involves the free Let's Encrypt SSL provider and the second one is an option if you have your own certificates ready to go.
Setting up HTTPS
Let's Encrypt
GitLab comes with the ability to automatically fetch and renew certificates from Let's Encrypt for the primary domain and the container registry for you. To get this running, you just need to specify...