# 在现有社区/域上安装时的迁移场景？

**URL:** https://meta.discourse.org/t/migration-scenarios-when-installing-on-an-existing-community-domain/86698
**Category:** Self-hosting
**Created:** [2018 年5 月 3 日 18:38 UTC](https://meta.discourse.org/t/migration-scenarios-when-installing-on-an-existing-community-domain/86698 "2018-05-03T18:38:35Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### 作者： ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### 发布日期： [2018 年5 月 4 日 23:25 UTC](https://meta.discourse.org/t/migration-scenarios-when-installing-on-an-existing-community-domain/86698/8 "2018-05-04T23:25:56Z")

</div>

> [@Queth](#):
>
> my VPS has apache, is it still possible to get discourse on that?

> [@Set up Discourse on a server with existing Apache sites](https://meta.discourse.org/t/how-to-set-up-discourse-on-a-server-with-existing-apache-sites/30013):
>
> It’s not as daunting as it sounds! While this may sound a bit intimidating at first, it’s really not all that bad. You basically need to do two things: Install HAProxy (or an alternative) which will take over port 80 and then divert your Discourse traffic to your docker container, and all your other sites to your usual Apache set-up. Let Apache know which port to listen for. While this is only a rough guide, it should do a good job of pointing you in the right direction. Let’s get star…

> [@Queth](#):
>
> lets say i want 2 instances of discourse, one to test, and one for production

It’s easiest to just set up another server, but you could use the same principle in the above link to have multiple Discourse instances on a single server with Apache reverse proxying both.

---

_[View the full topic](https://meta.discourse.org/t/migration-scenarios-when-installing-on-an-existing-community-domain/86698)._