# 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:** 12

<div class="post-metadata">

**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:** [February 19, 2021, 10:44am UTC](https://meta.discourse.org/t/high-availability-3-server-setup/180251/12 "2021-02-19T10:44:32Z")

</div>

You have two options:

- Use – I think it’s `./launcher start-command app` – on the fully set up machine (the “build machine”) to obtain a complete Docker command line
- Copy the app.yml over, and do what you just attempted (launcher start).

---

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