There are two ways go get certificates when using a non-common server,
For a first time issuance it seems to be easiest to use the standalone mode, since there isn’t a server running on port 443 yet. However, that will change once HTTPS is setup and live, because you don’t want a service interruption every 60 days for renewal (assuming that the revalidation time frame will be changed to the same as reissuance, so it’s always the same process instead of two different ones).
It’s a non-issue adding a route serving the ACME challenge once HTTPS is setup, but how can the manual mode be automated to prevent downtimes and / or expires, because it wasn’t automated? Does the challenge change every time?
I’d like to make HTTPS setups very easy using our application server, same applies to node apps. How can we make simple components that just have to be added to the router of choice to make automation possible where (almost) everything is configured through code instead of easy to parse and change config files?