Install discourse alongside WordPress in a dedicated server

[tharindu (Tharindu Pramuditha)]

I have asked a question earlier today about how to have multiple instances in a single server and what are the ideal configurations I need for the new server.

Multiple discourse instances in a single server

To determine that would depend on various factors. Have you considered profiling your current sites to determine potential bottlenecks? If downtime is your concern perhaps you could get a VPS with more than you need then scale back once everything is running smoothly. In my experience EC2 containers can get pricy rather quickly.

After hours of researching I have decided to use the dedicated server I already have in FastComet. The reason behind this decision is simply it has got a E5-2680 v3 @ 2.50GHz + 16gb of ram where I have installed few WordPress sites and it’s barely breaking a sweat.

My server is managed so I can have FastComet guys install the packages I want. What are the possibility to run discourse instances in this server? Is it possible to install docker containers on a optimized server for WordPress with nginx without having issues in the future?

[itsbhanusharma (Bhanu Sharma)]

@tharindu

What are the possibility to run discourse instances in this server?

Totally possible, Yet it needs some additional configuration over the vanilla install.

@tharindu

Is it possible to install docker containers on a optimized server for WordPress with nginx without having issues in the future?

Definitely possible, I’m running a similar setup but Future is unpredictable so I can’t speak of anything happening there.

[Cameron_D]

It’s possible. There is a guide here for getting Discourse running through another instance of nginx on the host:

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 the rest of the WordPress sites on the server can continue to run as they currently are.

[tharindu (Tharindu Pramuditha)]

Thanks for the hope @itsbhanusharma and @Cameron_D.

I have already sent this guide to FastComet team. Technical team will reach out to me and let me know if there’s any issues, otherwise I will surely breakdown the process into parts and publish a guide here so other users can save themselves from spending hours and hours figuring out what to do.

[itsbhanusharma (Bhanu Sharma)]

In case there is anything that they can’t figure out, be sure to post it here, I may be able to help out with the way I configure my own instance.

[ariznaf (fernando)]

Это именно то, что я искал.

У нас установлен Discourse на виртуальном сервере (конечно, с использованием Docker).

У меня есть простая установка WordPress на другом сервере (на другом поддомене), но я хотел бы перенести её на сервер с Discourse.

Я хочу установить контейнер Docker с WordPress и Nginx.

Но после прочтения всех упомянутых здесь постов я не уверен, как это сделать.

Здесь решение заключается в установке Nginx вне Docker, настройке отдельного сайта для WordPress и другого для Discourse, а также перенаправлении запросов Discourse через пайплайн.
Если я правильно понял, именно это и предлагает @Cameron_D.

Разве использование пайплайна для связи Nginx с установкой Discourse не будет медленнее?

Но в этом случае придётся подстраивать конфигурацию Discourse.

Есть ли возможность использовать Docker для установки ещё одного контейнера WordPress+Nginx, аналогичного установке Discourse?

Предполагаю, что уровень изоляции, обеспечиваемый Docker, хорошо подойдёт для избежания проблем с безопасностью.