letsencrypt support requires manual action

[msherman64]

Letsencrypt support currently requires manually requesting the first certificate.

This is because enabling letsencrypt support tells haproxy to use the TLS certificate, but letsencrypt runs after haproxy, and uses it for public access.

Therefore, enabling it only works if you already have a valid cert configured!

Currently, you can run the process manually, in this order.

1. Run deploy with letsencrypt disabled
2. use docker exec -it letsencrypt_certbot bash to manually run certbot
3. copy certificate out to site-config/certificates folder
4. enable letsencrypt, and re-run deploy.

[super-cooper]

Automate TLS certificate renewal for CHI-in-a-box sites