Run other websites on the same machine as Discourse

[pfaffman (Jay Pfaffman)]

Yes. The sockets are available outside of the container.

[shawa]

@pfaffman

Yes. The sockets are available outside of the container.

I am using OpenResty, which is running in a container. Do I just need to mount the /var/discourse/shared/standalone directory, where the nginx.http.sock file is stored, into the container?

[lega4]

@mottosso

Just wanted to share how I accomplished this, it was a little easier than I first thought.

From an already running machine, with Caddy acting as a reverse proxy for a number of existing Docker containers already.

1. Clone discourse as per the official instructions
2. Copy /var/discourse/samples/standalone.yml → /var/discourse/containers/app.yml
3. Fill in SMTP settings and website address
4. Comment out 443:443 from the expose: section
5. Replace 80:80 → 3001:80, 3001 being the port I’m serving via Caddy
6. Run ./launcher rebuild app
7. Done

That’s brilliant! This should be the actual “installation guide” and not the page that is currently written as “official”! Thousand thanks!

[Paracelsus]

A question:

Is the socket template (with nginx.http.sock in the conf file) a must if I want to setup other websites running on the same standalone server along with discourse?

We’ve recently migrated server and we ended up using port 8080 and nginx as reverse proxy but without using the socket template. Since it is working ok and I don’t see the point of using that method I would like to know if there’s no other way.

[pfaffman (Jay Pfaffman)]

If the port works for you then you don’t need the socket. Some people like the socket better for Reasons, but it doesn’t matter much.