# Pros and cons of installing Discourse on a NON-virtual machine?

**URL:** <https://meta.discourse.org/t/pros-and-cons-of-installing-discourse-on-a-non-virtual-machine/13677>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [12 Marzo, 2014 20:24 UTC](https://meta.discourse.org/t/pros-and-cons-of-installing-discourse-on-a-non-virtual-machine/13677 "2014-03-12T20:24:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [12 Marzo, 2014 22:28 UTC](https://meta.discourse.org/t/pros-and-cons-of-installing-discourse-on-a-non-virtual-machine/13677/6 "2014-03-12T22:28:24Z")

</div>

> [@snarke](#):
>
> Still, wouldn’t I make my life simpler by just using the Docker containerized install twice, once for the dev install and once for the production install?

In what sense do you mean dev install?

For actual development on Discourse, prefer Vagrant installed on your local machine.

For a staging server, yeah, I think two Docker installs would work. Hmm, can you have `containers/app.yml containers/app2.yml`? If you can get that to work, with a non-Docker nginx in front VHosting the two, you might be able to get a good setup.

---

_[View the full topic](https://meta.discourse.org/t/pros-and-cons-of-installing-discourse-on-a-non-virtual-machine/13677)._