# Help me setup many websites on one VPS

**URL:** <https://meta.discourse.org/t/help-me-setup-many-websites-on-one-vps/152585>\
**Category:** Self-hosting\
**Created:** [May 25, 2020, 8:14am UTC](https://meta.discourse.org/t/help-me-setup-many-websites-on-one-vps/152585 "2020-05-25T08:14:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix)\
**Post date:** [May 25, 2020, 9:05am UTC](https://meta.discourse.org/t/help-me-setup-many-websites-on-one-vps/152585/3 "2020-05-25T09:05:04Z")

</div>

> [@hinhsymo](#):
>
> Step 1 - Install Docker on Ubuntu 16.04  
> Step 2 - Install and configure discourse forum  
> Step 3 - Generate SSL Letsencrypt on Ubuntu 16.04  
> Step 4 - Install and configure Nginx as a reverse proxy for Discourse container  
> Step 5 - Discourse Web installer  
> Step 6 - Discourse additional configuration

The way I do this, since I like simple, is the "one container per web site method with each container using a `web.socketed.template.yml` template so each app (container) works with the nginx reverse proxy.

Something like this, roughly:

> [@](#):
>
> Step 1 - Install Docker on Ubuntu 16.04  
> Step 2 - Install and configure first discourse forum (app1,yml) using the socket template so the discourse app listens on the app1 shared unix domain socket  
> Step 3- Install and configure Nginx as a reverse proxy for your Discourse container  
> Step 4 - Generate the SSL Letsencrypt for your new FQDN (website)  
> Step 5 - Create a new container file (app2.yml) for your next website and build your new container and repeat.

Or, you can create all your containers first and do the entire `nginx` ssl (LetsEncrypt) part last, if you are feeling lucky.

This approach will take more disk space and memory but you will have the advantage of each web site running in it’s on isolated container.

I don’t think this method is “officially supported” but it’s easy enough to configure and support yourself, in my opinion. Setting up the socketed container is easy because you have an “official” Discourse template for this; and setting up the nginx reverse proxy to a unix domain socket is also well documented on the net (and there are some Discourse examples as well).

---

_[View the full topic](https://meta.discourse.org/t/help-me-setup-many-websites-on-one-vps/152585)._
