Set up Let’s Encrypt with multiple domains / redirects

Gemeenschaps wiki Systeembeheerders
,
176

Not likely. It’s the kind of thing that you’re likely to do exactly once, and you’ll do it when you’re already mucking with app.yml.

I’ll see about making a PR that adds it to the standalone.yml, though.

And with this in place, this is much simpler!

4 likes
177

bedankt hiervoor, ik heb lokaal templates/web.letsencrypt.ssl.template.yml aangepast, maar dit maakt mijn leven zoveel gemakkelijker!

1 like
178

Do we need to include the (OG) hostname in this, or just the aliases?

179

Alleen de aliassen. De hostnaam is de hostnaam.

1 like
180

Dus zo dan?

env:
  DISCOURSE_HOSTNAME: domain.com
  DISCOURSE_HOSTNAME_ALIASES: www.domain.com,otherdomain.org,www.otherdomain.org
1 like
181

Wrestling philosophically with the meaning of ‘alias’, I included both urls that I want to lead to my site: nzarchitecure.net.nz and www.nzarchitecture.net.nz with no obvious ill effects (& presumably no benefit either).

1 like
182

Kan standalone.yml worden gewijzigd door of opgedragen worden om beheerdersinstellingen te lezen binnen een draaiende instantie van Discourse?
Zo ja, dan zou dat een grote hulp zijn voor nieuwe gebruikers en degenen die domeinen willen migreren of aliassen willen toevoegen - één zorg minder om te onderzoeken en op te lossen.

183

No. It would be really bad if the jobs running in the container could change things like app.yml. Actually, a good security practice is to put stuff like S3 keys in the yml file so that they are hidden from the Discourse interface.

Again, it’s very rare that you make changes like what domains need to be redirected, and they require other things, like DNS settings. The time to do it is when you set up Discourse, and when you set up Discourse, you’re mucking with the yml file.

1 like