# Discourse double branch offices installation **URL:** \ **Category:** Self-hosting\ **Created:** [September 22, 2017, 5:55pm UTC](https://meta.discourse.org/t/discourse-double-branch-offices-installation/70595 "2017-09-22T17:55:54Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [September 22, 2017, 7:55pm UTC](https://meta.discourse.org/t/discourse-double-branch-offices-installation/70595/4 "2017-09-22T19:55:56Z")
I think it would be something like this: - split the Postgres database and Redis server out of the container (see #howto about using an existing database server) - set up streaming replication for Postgres and a sentinel cluster for Redis (a 1-1-1 cluster, with the 3rd “C” server cloud somewhere) - set `DISCOURSE_REDIS_SENTINELS` in office A to the addresses of sentinels A,C - copy the web\_only.yml to a server in office B - set `DISCOURSE_DB_REPLICA_{HOST,PORT}` to the office B replica, but DB\_HOST/PORT to the office A ([discourse/config/discourse\_defaults.conf at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/config/discourse_defaults.conf#L46)) - set `DISCOURSE_REDIS_HOST/PORT` to the office B Redis server - set `DISCOURSE_REDIS_SENTINELS` in office B to sentinels B,C Aaand there’s more to cover that I haven’t got into yet, like synchronizing uploads/backups (use S3 I guess?) Now that I’m writing this down, I’m not actually sure that anyone has actually done this before. You might run into problems that require code changes. edit: after reading about redis sentinel some more, I think my above advice is at least a little bit wrong. So, good luck! --- _[View the full topic](https://meta.discourse.org/t/discourse-double-branch-offices-installation/70595)._