So this is actually really really cool. Hear me out.
Automatic staging deployments
Upon pushing new changes to the Git repository we will from now on automatically deploy those changes to a staging server. This will enable us to actually have a look at the changes without having to check out the entire repo and go through all the hoops of switching branches, re-migrating the database (which can be a pain of you've done migrations in your own branch), starting up a slow IDE and all the sorts.
GitLab will show a link to the deployment right from within a Merge Request (as you can see in this MR as well, hopefully
Upon merging a branch (or MR) back into master, the deployment will automatically get deleted from the web server.
HTTPS support
All pages get served over HTTPS, as is required for voice and camera features to work in Chrome. There's just one (minor, in my opinion) inconvenience: Let's Encrypt does not offer wildcard certs (*.gac.robbytu.net) until February of 2018. As a work around I have created a self-signed wildcard cert. Works perfectly fine, but you will have to press the annoying "Yes, I know what I am doing and want to continue to this 'insecure' site"-button and that's fine.
Nb. You can of course install the certificate to your local machine so that you will no longer see the "You're not secure" windows.
MR links
This MR includes code from !27 (merged) (without a good reason - I forgot to checkout master beforehand. Sorry about that). Please first review !27 (merged) before merging this MR. You can, of course, (and I highly encourage you to do so,) cherry pick the GitLab CD changes to your own branches, but please refrain from merging this branch into your own when this MR or !27 (merged) have not been accepted.