# Pros and cons of a multisite installation

**URL:** <https://meta.discourse.org/t/pros-and-cons-of-a-multisite-installation/90584>\
**Category:** Self-hosting\
**Created:** [6월 24, 2018, 10:03오전 UTC](https://meta.discourse.org/t/pros-and-cons-of-a-multisite-installation/90584 "2018-06-24T10:03:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [6월 24, 2018, 8:22오후 UTC](https://meta.discourse.org/t/pros-and-cons-of-a-multisite-installation/90584/3 "2018-06-24T20:22:56Z")

</div>

> [@tophee](#):
>
> But what about support, for example? If I search meta for a solution to an issue and find something, will it automatically apply to my multisite install, even though the original topic doesn’t explicitly deal with multisite?

Typically yes – however, for some steps, you’ll need to make sure you work on the correct instance. The key is to set an environment variable like `RAILS_DB=myfancypantsinstance1` e.g. when entering the rails console.

This is why I recommend making the first instance on a multisite host a test instance: If you ever forget to specify the instance, you’ll target your test instance, which is probably safer than working with a production instance by accident 😉

---

_[View the full topic](https://meta.discourse.org/t/pros-and-cons-of-a-multisite-installation/90584)._