# Multiple Standalone containers instead of multisite?
**URL:** https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524
**Category:** Self-hosting
**Tags:** hosting
**Created:** [November 25, 2014, 10:56pm UTC](https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524 "2014-11-25T22:56:02Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@helmi](https://meta.discourse.org/u/helmi)
#### Post date: [November 25, 2014, 10:56pm UTC](https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524/1 "2014-11-25T22:56:03Z")
Hi,
to be honest i’m not so much into docker for now but i was wondering if it could probably be a good alternative to a multisite installation to have just multiple standalone containers next to each other on one VM. Name based hosting could be solved with an reverse proxying nginx and some stuff that is “global” in multisite installation (like the admin email-accounts, smtp settings and other stuff) could be easily separated here.
Is there anything that would make this a problem? Probably the multiple instanced of Redis or Postgresql (that’s where i’m lacking knowledge in relation to Docker).
Thanks for helping,
Frank
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [November 26, 2014, 12:46am UTC](https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524/2 "2014-11-26T00:46:22Z")
You can basically just follow this guide twice:
> [@Run other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247):
>
> @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…
---
### Author:  [@helmi](https://meta.discourse.org/u/helmi)
#### Post date: [November 26, 2014, 7:38am UTC](https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524/3 "2014-11-26T07:38:21Z")
Thanks, riking, but you probably just got me wrong. I know about the reverse proxying and could get it to work without a problem i think (thanks anyway for posting that link).
My question was more about discourse itself in multiple instances. Is it suitable to have standalone-container. each with their own Redis and Postgresql instance or does this probably eat up too much resources or cause trouble? I’m relatively new to docker so i’m not sure how multiple instances of the same daemons get handled and if it’s a good idea.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [November 27, 2014, 2:27am UTC](https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524/4 "2014-11-27T02:27:15Z")
You could go either way, really. If you do 2-web 1-data, you’ll have to set different database names. If you do 2-standalone you don’t really have to worry about anything, but it might be performing extra work. It’s your call.
Also, I would recommend a 2GB with swap minimum.
---
### Author:  [@helmi](https://meta.discourse.org/u/helmi)
#### Post date: [November 27, 2014, 9:32am UTC](https://meta.discourse.org/t/multiple-standalone-containers-instead-of-multisite/22524/5 "2014-11-27T09:32:51Z")
ok great, thanks. I’m currently on a 4GB VM with swap but resources aren’t the biggest problem here as the bare metal machine itself is mine and has some resources left. I’ll try around that way.