Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #328
This PR adds Let's Encrypt integration. It will automatically create a valid, production-ready SSL certificate through LE and configure your WP site to use it.
These certifications expire every 90 days so there's a cronjob to renew them monthly.
There's a new
provider
option under thessl
object for each WP site. Valid options are:self-signed
- used in developmentmanual
- when you already have a key and cert you just want copied overletsencrypt
- invokes automatic LE certificate flowTesting
letsencrypt_ca
fromgroup_vars/all/main.yml
if you want a real production cert. Otherwise you are using Let's Encrypt's staging server and the CA isn't verified in browsers. Note: LE production has rate limits. So don't exhaust the limit just testing unless you need a real cert.Todo:
letsencrypt
(toggle via variable)