Is the Bitnami container also compiling Discourse completely new when updating it, like the official one?
The variable seems to be defined here:
The current_hostname variable is set here:
The force_hostname variable is declared in the site settings template here:
As it is hidden, it cannot be changed in admin settings. As other site settings, I assume it would be stored in the database. I searched a database dump of our instance and force_hostname is not set or even declared. In our official discourse container YAML we have DISCOURSE_HOSTNAME assigned, but I guess this is a global setting, not a site setting, so this seems to be enforced differently.
current_hostname seems to be obtained from the current connecting, i.e. dynamic. But I cannot see where exactly it is defined, probably an external module/gem:
I’m not sure what the Bitnami container does with the DISCOURSE_HOST setting, so at least you could search your database for force_hostname until we find out more about how DISCOURSE_HOSTNAME from official container is stored and enforced.
Thank you for your support so far! I was, comparing to you findings, also thinking about config my install as single multisite. This could maybe make it work, but it’s indeed a matter of trying to sort things out where I have the feeling that Bitnami doesn’t change anything on Discourse itself; so why this issue indeed.
Okay so currently I fail do understand where/how both Discourse container variants internally apply the hostname based on the container YAML.
Does the Bitnami container composition not include another webserver but expose the Discourse web port directly? The official containet has another Nginx in front of Discourse, something I actually wanted to get rid of if possible, as we have another Apache webserver outside of the container already.