elyograg
commented
1 year ago After evaluating what I can find, I have determined that I won't be saving myself any time or effort by using dehydrated. I already have code using certbot that I can use in my automation efforts, and I would spend as much time building automation for dehydrated as I would with my own code.
I'm looking for some help in configuring dehydrated to automate certificate renewal for my company. We primarily use wildcard certificates.
I built an app using php, bash, and certbot designed for human interaction. It lets people generate/renew lets encrypt certs defined in its database. It uses '--dns-route53' to automatically handle the validation. This works quite well ... it only takes a few clicks and about 30 seconds for someone to get an updated certificate.
I've been looking over the docs for dehydrated. I haven't been able to work out exactly what dehydrated config to create to duplicate this system for automation. Boss asked me to look into dehydrated as an alternative to modifying my webapp for automation as well as human interaction. My automation would set environment variables for the AWS key and secret that automatic route53 validaton needs, but I haven't seen any way to tell dehydrated to use route53 validation.
What I am hoping to find is fully fleshed out example configs. There are docs on each config file, but I have not seen any complete sets of example config files. Those config file sets should also come with an explanation of how the config files interact with each other.