# Splitting a site into two parts

**URL:** <https://meta.discourse.org/t/splitting-a-site-into-two-parts/269649>\
**Category:** Product Support\
**Created:** [June 26, 2023, 3:09pm UTC](https://meta.discourse.org/t/splitting-a-site-into-two-parts/269649 "2023-06-26T15:09:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![MikeNolan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mikenolan/32/297597_2.png) [@MikeNolan](https://meta.discourse.org/u/MikeNolan)\
**Post date:** [June 29, 2023, 2:05pm UTC](https://meta.discourse.org/t/splitting-a-site-into-two-parts/269649/4 "2023-06-29T14:05:48Z")

</div>

I decided to go with [lists.tssi.com](http://lists.tssi.com) for the gateway site and [x.tssi.com](http://x.tssi.com) and [y.tssi.com](http://y.tssi.com) for the separate communities as opposed to [x.lists.tssi.com](http://x.lists.tssi.com) and [y.lists.tssi.com](http://y.lists.tssi.com). Couldn’t get the latter to work, possibly an ngingx setup issue, it kept rerouting requests for [x.lists.tssi.com](http://x.lists.tssi.com) or [y.lists.tssi.com](http://y.lists.tssi.com) to [lists.tssi.com](http://lists.tssi.com) rather than to the Discourse server.

But I can get the other to work, and a working solution is better than a non-working one. 🙂

---

_[View the full topic](https://meta.discourse.org/t/splitting-a-site-into-two-parts/269649)._