# High Availability 3 Server setup

**URL:** <https://meta.discourse.org/t/high-availability-3-server-setup/180251>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [February 18, 2021, 8:02pm UTC](https://meta.discourse.org/t/high-availability-3-server-setup/180251 "2021-02-18T20:02:32Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![andy212](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@andy212](https://meta.discourse.org/u/andy212)\
**Post date:** [February 19, 2021, 5:52am UTC](https://meta.discourse.org/t/high-availability-3-server-setup/180251/11 "2021-02-19T05:52:49Z")

</div>

Okay. So I have now have a working discourse on a single machine. I have two other machines. The docker guest /shared volume is pointed to an NFS directory to allow all machines to access the uploads (esp. logos, etc).

I have copied the docker images to the machines 2 and 3 (`docker save -o app-image local_discourse/app` and then `docker load -i app-image`.

I was under the impression that a simple `./launcher start app` would work, but it attempts to check containers/app.yml.

Will I run into problems if I allow the app.yml to be checked (and changes made) to the DB from machine 2 and 3?

Is there a better way to have three machines running a single setup?

---

_[View the full topic](https://meta.discourse.org/t/high-availability-3-server-setup/180251)._