-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wildcard certs #387
base: master
Are you sure you want to change the base?
Wildcard certs #387
Conversation
IMPORTANT: Merijn please run the proper roles for make sure it works xoxo |
This seems to fail for https://dev.svsticky.nl/ ( |
20fe909
to
5966b25
Compare
Nope, I only had to add the hostname as a seperate domain to the certbot command and poof it's working |
5966b25
to
706073a
Compare
TODO: Create a loop to request certs for
|
--cert-name {{ item }} | ||
--dns-digitalocean | ||
--dns-digitalocean-credentials /etc/letsencrypt/certbot-creds.ini | ||
--domain "*.{% if 'staging' in group_names %}dev.{% endif %}{{ item }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note: to make this work, every domain should get an extra domain record (dev.domainame
pointing to the staging server).
Yay! Very nice! I think everything is fixed with this, just have to run all the updated tasks to make sure all the subdomains are still working with the wildcard cert.
Maybe we can also destory a bit of the websites.yml with this PR? Who knows? Only time will tell..