Does this package only support HTTPs domain validation? Would be nice if it would help with DNS based validation as well.
I'm using github.com/hlandau/acme/acmeapi at the moment, but the API isn't documented well. Their command line client is better, but library is more convenient when you have custom storage for certs.
Also a question for someone who has it running in production. What is the best way to handle TOS updates? Do you just setup some notifications when this happens or accept automatically? I'm not sure how often this happens, but the last update was this month.
I think, that vendor prefixes prevents us from getting into incompatibility nightmare.
If they were dropped for less stable css properties, web developers would start using css hacks again.
Because newer css properties don't have consistent behavior across browsers (border-radius don't work properly with border-style in firefox),
and experimental properties can even have different syntax (for example css gradients in safari and firefox).
I'm using github.com/hlandau/acme/acmeapi at the moment, but the API isn't documented well. Their command line client is better, but library is more convenient when you have custom storage for certs.
Also a question for someone who has it running in production. What is the best way to handle TOS updates? Do you just setup some notifications when this happens or accept automatically? I'm not sure how often this happens, but the last update was this month.