# Creating a duplicate of production environment

**URL:** <https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966>\
**Category:** Self-hosting\
**Created:** [5월 2, 2017, 3:38오후 UTC](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966 "2017-05-02T15:38:05Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![keith1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/keith1/32/178982_2.png) [@keith1](https://meta.discourse.org/u/keith1)\
**Post date:** [1월 7, 2019, 2:22오전 UTC](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966/11 "2019-01-07T02:22:40Z")

</div>

I went about this in a different, although slightly uglier way - I cloned my entire droplet on DigitalOcean, then logged into the droplet and disabled all of the ssl/https settings in the app.yml. This at least gave me a clone of my community content to screw with settings on.

I have no elegant way to migrate changes from my test server to the live server except by manually repeating, so this is still total amateur hour, but it at least let’s me explore without breaking the live server.

---

_[View the full topic](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966)._