The discussion revolves around installing Discourse on a machine with existing Nginx and SSL. helmi is seeking guidance on creating the app.yml file from scratch, as the default setup doesn’t work when port 80 is already in use. Falco suggests using the quick guide and running everything inside the container, but helmi explains that Nginx is already running on port 80 for other projects, making proxying necessary.
Falco advises editing app.yml to change the exposed port and rebuilding, then configuring Nginx to proxy to that port. helmi successfully installs Discourse after creating the app.yml file, but encounters issues with loading assets when accessing through the proxy. They question whether the SSL cert needs to be connected to the backend, as they thought terminating SSL at Nginx should be sufficient.
I have an existing machine with nginx and SSL running (also for the domain that is supposed to use discourse later).
I found quite some hints about how to proxy to discourse through nginx but none of the approaches this from a fresh installation. As ./discourse-setup basically doesn’t even start when port 80 is in use already I’m a bit lost when it comes to changing the app.yml that isn’t yet created.
I’m sure I can create it from the bottom up but I don’t know how.
Do you really need a nginx proxy with Discourse? That’s an advanced setup. We really recomend sticking to the quick guide and running everything inside the container and using a DNS subdomain for the forums.
the machine where discourse will be running is already running Nginx on port 80 for different projects and it has to go there. Therefore proxying to nging will most probably the way to go.
I’m not afraid of doing advanced setups, I have just not written the configuration file manually yet and it doesn’t seem to work any other way here.
The cert also already is existing and is perfectly well for the domain/subdomain I’m planning to use.
