Nginx + discourse

[Honey]

On my vps I use primarily nginx for a php type forum. I also am running NodeBB (node.js) proxied through nginx. The point being port 80 belongs to nginx. I believe this will work, but I’d like some feedback.

app.xml

## which TCP/IP ports should this container expose?
expose:
  - "81:80"   # fwd host port 80   to container port 80 (http)
  - "2222:22" # fwd host port 2222 to container port 22 (ssh)[/code]

nginx
[code]server {
    listen 80;

    server_name example.com;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:81/;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Thoughts?

[wesochuck (Wes Osborn)]

You might want to take a look at this post for more information:

Run other websites on the same machine as Discourse

@pfaffman edited this heavily 2022.02.24. Blame me if it’s broken. If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container. NOTE: This is for advanced admins This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working. You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will …

Haven’t done it myself, but looks pretty detailed and might send you in the right direction for your project.

[Honey]

I’m aware of that, but I don’t think you’ve answered my question (your post also got cut off)

Do you see the above configuration as a possible working solution? Discourse is not yet installed and I plan on using the above app.xml to install it. The nginx should then act as a proxy.

If you don’t know, please say you don’t know. That is a perfectly acceptable answer.

[codinghorror (Jeff Atwood)]

Post is not cut off, it is a summary generated from the link. Click through to view. Like any other link on the web…

You can also click on the top of the summary anywhere around the chevron arrow to expand it in place, rather than visiting the URL.

[Honey]

Alright, I missed that.

I decided to try my configuration anyways and answer my own question. The answer is YES it works using my configuration found in post #1

Nginx + discourse

On my vps I use primarily nginx for a php type forum. I also am running NodeBB (node.js) proxied through nginx. The point being port 80 belongs to nginx. I believe this will work, but I’d like some feedback. app.xml ## which TCP/IP ports should this container expose? expose: - "81:80" # fwd host port 80 to container port 80 (http) - "2222:22" # fwd host port 2222 to container port 22 (ssh)[/code] nginx [code]server { listen 80; server_name example.com; location / { …

[wesochuck (Wes Osborn)]

@Honey

I’m aware of that

Let us know what prior research you’ve done in the future so we can skip recommending anything you might have already seen.

@Honey

please say you don’t know

See:

@wesochuck

Haven’t done it myself

@Honey

I plan on using the above app.xml to install it.

Do you mean app.yml ? From my linked article:

@riking

This is where we change how Discourse actually gets set up. We don’t want the container listening on ports - instead, we’ll tell it to listen on a special file.

Change your /var/discourse/containers/app.yml to look like this:

So, I would say that while your proposed app.yml file might work, it would not be the preferred/supported method of doing what you’re trying to accomplish.

[Honey]

I do apologize. I’m new to discourse and your post appeared to be cut off. So from my limited perspective it originally appeared to offer no information.

The only question I really was asking was if my config looked like it would work or if anyone else had tried such a configuration?!

I decided to proceed forward and my config does work.

[wesochuck (Wes Osborn)]

Understood, no hard feelings. Good luck with your setup. Do consider my warning though that while your method may work, you might encounter support issues that this community won’t be able to help you with because your setup is different than the one recommended by a Discourse team member.

[codinghorror (Jeff Atwood)]

Seems like @honey knows what s/he is doing. Good work!

[PabloC]

Thanks @Honey!

Also, it is amazing how well Discourse is indexed on Google.

Kudos guys