Set up Let’s Encrypt with multiple domains / redirects

Just noting I’m currently attempting on rolling this into env vars to handle directly in discourse_docker, something like a comma separated list of hostname aliases. Seems like a common enough use case to handle directly.

It’s going to make it easier to configure for this case, so no one will need to make modifications to their app.ymls

My current plan is with DISCOURSE_HOSTNAME: www.domain.com

Allow for env like:
DISCOURSE_HOSTNAME_ALIASES: domain.com,other.domain.com would pull the cert, valid for all hostnames.

(While I’m there, let’s encrypt auto renewals also don’t seem to be working properly so I’m fixing those up too)

8 likes