__letsencrypt_cert rewrite and subtypes, analyse phase
what do we win if we have type with subtypes?
how do we decide in main type which subtype to use?
what's default fallback?
__letsencrypt_cert rewrite and subtypes, analyse phase
- For us, support for different challenge types, i.e. DNS validation, would be really useful since we use Let's Encrypt certificates also for…
__letsencrypt_cert rewrite and subtypes, analyse phase
- that looks nice
- agree
- me neither because I don't use it, but some maybe does
- but then again ju can use extra-args for standalone
__letsencrypt_cert rewrite and subtypes, analyse phase
shortest possible working type should be something like this:
__letsencrypt_cert example.com --mail hostmaster@example.com --webroot /var/www
now, how we decide which backend? we don't want…
__letsencrypt_cert rewrite and subtypes, analyse phase
I'm starting to get annoyed by this, bit me again today - __letsencrypt_cert is somewhat broken and needs to be fixed.
I'll do some priority ordering...
__letsencrypt_cert rewrite and subtypes, analyse phase
I agree with --type defaulting to certbot. I guess that's what most users would expect.
Users who want a different backend, can just use the --type parameter.
Not sure about the --webroot.…