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

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 need to copy and edit samples/standalone.yml with your favorite tex…

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 설정을 조정해야 합니다.

Discourse 설치 방식과 유사하게, Docker를 사용하여 WordPress+nginx 컨테이너를 추가로 설치할 수 있는 옵션이 있을까요?

Docker가 제공하는 격리 수준 덕분에 보안 문제를 피할 수 있을 것이라 생각합니다.