balupton
(Benjamin Lupton)
February 5, 2024, 7:39pm
1
Has the force_https
setting been removed? Or is does it not show up if certain templates are used. Here are the templates I’m using:
templates:
- "templates/postgres.template.yml"
- "templates/redis.template.yml"
- "templates/web.template.yml"
- "templates/cloudflare.template.yml"
- "templates/web.ssl.template.yml" # https
- "templates/web.letsencrypt.ssl.template.yml" # https
# - "templates/web.ratelimited.template.yml" # not needed
I don’t think so. I see no changes around force_https
and I can still see the setting
`
I think there is some magic that hides it if you meet certain criteria:
pfaffman
(Jay Pfaffman)
February 5, 2024, 8:57pm
4
Without finding the code, I think what happens is that if you have a certificate, DISCOURSE_FORCE_HTTPS
gets set to true, so it’s hidden from the UX.
4 Likes
I was looking for this the other day. Is it this bit:
6 Likes
pfaffman
(Jay Pfaffman)
February 5, 2024, 9:18pm
6
That’s it! The other way to get stuff into config/discourse.conf
is setting an ENV variable, which results in something writing those out to that file just like that.
3 Likes
system
(system)
Closed
March 6, 2024, 9:18pm
7
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.