Make it easier to try out SSL with Sourcegraph #2285
Description
It's unlikely that a user will want to share Sourcegraph with the rest of their team until they have HTTPS set up.
Provisioning a real SSL certificate involves:
- buying a domain name
- buying a cert / setting up let's encrypt (might involve adding/modifying DNS records)
- configuring Nginx to use the certificate
- changing Sourcegraph's external URL to point to the purchased domain name
Using a self-signed certificate skips most of the above steps. Self-signed certificates won't be recognized by any browsers, but a user would probably willing to accept this tradeoff if it makes it easier to quickly demo/share Sourcegraph with the rest of their team. If the browser warnings become too annoying, they can tell people to install the fake certificate authority on their local machines or just provision a real certificate.
We can even use terraform scripts / pre-baked AMIs to skip most of the boilerplate involved with pointing Nginx at the self-signed cert and configuring Sourcegraph's external URL.