I've found this topic regarding automation of http certificate creation: generate http certificate non interactive, as I was wondering the same thing: why can't I use the same advanced feature of using a
yaml file containing all my relevant information in order to generate my certificates for HTTP.
I know the difference of
http layer. but I'm wondering:
- do they need to be different? (all the
docker-composeexamples are using the same for
transport) if yes, why ?
- is there a difference when calling the
certoption? or can I just re-use the
certoption for my http certificates ?
thank you in advance for your explanations and/or best practices.
docker tag was added automatically, but I'm not asking about docker deployment specifically!