As you've mentioned this only allows to provision the certificate and different steps are required for renewal. Would you like to inform the user about this and how to go about renewal?

Presently pairing the service in a compose config next to the DMS service would run that service and command each time the mail-server is brought up with a docker-compose up -d, is that going to be a concern? Should it be treated as a separate compose file?

I've not reviewed the other guides on this page, they may have a similar concern but not one you need to worry about 👍

I came across a very similar step-by-step guide that shows that renewal command is pretty much the same but includes renew instead of certonly, they also have a few extra options in their commands (also via a docker-compose file) that might be worthwhile.

It seems common to just setup a cron or systemd timer on the host to schedule renewals with Certbot?

I'm not blocking approval on this, but it would be appreciated if addressed 😅

Sure, it'd be better if we add that part about renewal, gonna working on this part later and expect to create a commit later today

I've completed add documentation for renewing certificate in 8560bdf, waiting for github-action to complete building preview