# Looking for Production Discourse Instructions

**URL:** https://meta.discourse.org/t/looking-for-production-discourse-instructions/68096
**Category:** Self-hosting
**Created:** [August 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:** 8

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 14, 2020, 12:26am UTC](https://meta.discourse.org/t/looking-for-production-discourse-instructions/68096/8 "2020-02-14T00:26:06Z")

</div>

> [@Julian\_Labuschagne](#):
>
> Can we save the built images from the script to a private docker registry to in turn add to our docker-compose.yml files that could be used for stack deployments?

Yes and that is the way to go.

> [@Julian\_Labuschagne](#):
>
> Why adopt shipping your project on container technology so very early on, only to frustrate users later in the future

They bought bad crystal balls to predict the future. Told em to buy better ones for the next project 😂

Being serious, like you asked it’s easy to save the resulting image in a container registry and deploy it afterwards using the tool you like the most.

And since you can run said container using some bash scripts, puppet, chef, ansible, terraform, backed into the AMI, user-data script, docker swarm, docker compose, kubernetes, capistrano, AWS ECS or many other ways it would be very out of scope for us to dictate your infrastructure management.

---

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