# Staging instance on same Production instance Docker Server?

**URL:** https://meta.discourse.org/t/staging-instance-on-same-production-instance-docker-server/134990
**Category:** Self-hosting
**Created:** [December 3, 2019, 6:33pm UTC](https://meta.discourse.org/t/staging-instance-on-same-production-instance-docker-server/134990 "2019-12-03T18:33:35Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [December 3, 2019, 6:42pm UTC](https://meta.discourse.org/t/staging-instance-on-same-production-instance-docker-server/134990/2 "2019-12-03T18:42:27Z")

</div>

You can do that if you have something like traefik reverse proxying to multiple containers. It’s lots simpler to have two droplets, one of which you could delete when you’re not using it. That way, you’ve still got a [Standard Install](https://meta.discourse.org/t/142537?silent=true) that’s easy to debug as well as get help here.

EDIT: And if you want a configuration that includes Traefik as the front end with multiple Discourse, WordPress and Ghost containers as well as prometheus and Graphana containers to make [pretty graphs](https://meta.discourse.org/t/prometheus-exporter-plugin-for-discourse/72666) I can do that for you.

> [@mreach](#):
>
> Ultimately, after config and setup, my thought is to sync the production database to staging.

My preferred way to do that is by keeping backups in an S3 bucket (or GCP or Digital Ocean equivalent). You could have two containers share a backup mount if they’re on the same server, but the S3 solution is really nice and makes it easy to move to a new server should disaster strike.

---

_[View the full topic](https://meta.discourse.org/t/staging-instance-on-same-production-instance-docker-server/134990)._