Installation Help required

[umardraz]

Hello

I want to install Discourse, but before installation I want to ask few things.

I have already Postgress database on dedicated vm and I can access that postgress database in my docker containers. I also have a nginx running on a separate vm and that nginx can also access dockers exposed ports.

So I want a very simple installation of discourse without any database, nginx, redis etc so my goal is a very simple discourse docker installation. So would you please help me what exact I need to do. Where I need to set the postgress database ip, username and password.

[TheBestPessimist]

I think you should start by looking at these (you know there’s a search button up there on the right, right?):

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 …

and also at the posts linked here

Move from standalone container to separate web and data containers

Is this still the good tutorial? Or should follow or Right now both of those tutorials still leave me with questions :-/.

[umardraz]

Well here is my existing setup

10.0.0.20 = Postgress machine
10.0.0.21 = Nginx machine
10.0.0.22 = A machine with Docker Installation and already running some container with docker default network (172.17.0.1)

I already have running 2 containers of nodejs app on my Docker Machine with 3001 and 3002 port

And from my nginx I am using proxy pass and send the traffic on these ports e.g.

nodejs1 -> 10.0.0.22:3001 nodejs1 container
nodejs2 -> 10.0.0.22:3002 nodejs2 container

Now I want to launch a Discourse container on my docker machine with port e.g 3003 and then from nginx I can send traffic on this container for my domain e.g discourse -> 10.0.0.22:3003

[umardraz]

Hello,

Finally I got samples/web_only.yml file and that was enough to understand how we can launch web only container.

[TheBestPessimist]

Gratz.!

You have to try a little by yourself if you want to learn this stuff :P.

[merefield (Robert)]

Interesting challenge.

Won’t a bespoke setup like this cause you a lot more work and frustration during the full lifecycle, though?

You could learn a lot I suppose? But can’t see any other advantages? Saves a small amount of space?

[itsbhanusharma (Bhanu Sharma)]

I don’t think that would be the case!
On the contrary, there’s a considerable amount of added performance by running data separately. There are even tutorials about it:

Configure Discourse to use a separate PostgreSQL server

Let’s say you’re using AWS RDS, or an existing PostgreSQL server managed elsewhere. It’s fairly straightforward to get Discourse to use such a setup, without needing to grant superuser privileges to anything that Discourse itself runs. Here’s how. Prerequisites Discourse requires PostgreSQL 13; if you try to run on a newer or older version, it might work, but we don’t guarantee it, and if something breaks in the future, you get to keep both pieces. We also require some extensions that are di…

[merefield (Robert)]

What about the upgrade process? Would it impact the normal simplicity of that?

[itsbhanusharma (Bhanu Sharma)]

You already know you’re doing advance things.

Your web container will rebuild normally, the upgrades from docker manager work too

Only thing you have to be mindful of managing postgres upgrades on your own.

If you know what you’re doing (You obviously will if you are running a separate postgres server already) then it shouldn’t be too big of a deal!