4 ms·
Just the other day, we finished a "dry run" deployment of our new app for small businesses on a Digital Ocean droplet running Debian and Apache (our app is Embe
by ralmidani 11y ago
Just the other day, we finished a "dry run" deployment of our new app for small businesses on a Digital Ocean droplet running Debian and Apache (our app is Ember and Django). Let's Encrypt was the final step.
We followed the instructions provided by DO[0], and aside from our mistake of leaving a previous attempt as a Virtualhost on port 443, the client just works out-of-the-box.
It automatically detects which file has the Virtualhost for port 80, asks you if you want to force redirect to https, copies your script to a new file with a Virtualhost on port 443 (adding SSL and telling Apache where to find the certs), and enables the site for you. Needless to say, my pair programmer and I were impressed thoroughly.
[0]https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-14-04 https://www.digitalocean.com/community/tutorials/how-to-secu...
- obituary_latte 11y agoSorry if I'm not understanding, but so it generates an httpd.conf for you?
- schoen 11y agoThe apache plugin for the Let's Encrypt Python client can edit apache configuration files (one of the most complex and hard-to-get-right but also one of the most convenient features of the client). There is also an nginx plugin which is significantly more experimental and which also edits nginx configuration files.
- ralmidani 11y agoWe had our sites configured in sites-enabled (ember.conf and django.conf). The LE client copied everything over to new files with encryption enabled, and had the old port 80 Virtualhosts redirect to the port 443 Virtualhosts.