# Looking for Production Discourse Instructions

**URL:** https://meta.discourse.org/t/looking-for-production-discourse-instructions/68096
**Category:** Self-hosting
**Created:** [15 באוגוסט,‏ 2017,‏ 6:27pm UTC](https://meta.discourse.org/t/looking-for-production-discourse-instructions/68096 "2017-08-15T18:27:02Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [17 באוגוסט,‏ 2017,‏ 1:45pm UTC](https://meta.discourse.org/t/looking-for-production-discourse-instructions/68096/4 "2017-08-17T13:45:15Z")

</div>

> [@Dan\_Healy](#):
>
> In a production HA environment, it is not acceptable to have a single container run Rail,Redis, Postgresql, and Nginx.

Sure, and we do not do that in our production instances, see: [discourse\_docker/samples at master · discourse/discourse\_docker · GitHub](https://github.com/discourse/discourse_docker/tree/master/samples)

> [@Dan\_Healy](#):
>
> It’s not clear to me if the current Discourse Docker solution will run properly on an existing Docker Cluster with many other containers already running

Runs fine for us

> [@Dan\_Healy](#):
>
> Our environment already has HA Postgresql, Redis, and a Docker Cluster - These should be leveraged

Nothing stopping you leveraging that pg and redis location are passed in via environment vars

> [@Dan\_Healy](#):
>
> The Discourse rails app should have the ability to start with a ‘docker stack deploy’ function, not a ./launcher script.

This did not exist 3 years ago. So, yeah … maybe … but it would require a ton of new work.

Feel free to read through: [Can Discourse ship frequent Docker images that do not need to be bootstrapped?](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205)

---

_[View the full topic](https://meta.discourse.org/t/looking-for-production-discourse-instructions/68096)._