# Staging / Production Help **URL:** \ **Category:** Questions / Help\ **Tags:** wishlist, flyctl, login-only\ **Created:** [December 2, 2024, 11:12pm UTC](https://community.fly.io/t/staging-production-help/22899 "2024-12-02T23:12:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![paul\_hermans](https://avatars.discourse-cdn.com/v4/letter/p/848f3c/32.png) [@paul\_hermans](https://community.fly.io/u/paul_hermans)\ **Post date:** [December 2, 2024, 11:12pm UTC](https://community.fly.io/t/staging-production-help/22899/1 "2024-12-02T23:12:55Z")
I am new to [Fly.io](http://Fly.io) and so far finding it hard to understand / follow, but I managed to get my django web app up and running. Now I have made some changes to it that will affect the DB and before I deploy to the production app I want ensure that I migrate properly and don’t break anything. To do this I was assuming I could “clone” the current state of the production app (Machine, Volume, Secrets) to a new app called “staging” and then I could deploy changes to the staging app and see how it goes…when (not if) it fails I could figure out why, fix stuff in my code and do it again. Repeat until the update is smooth…but I can’t figure out how to do this. So far I have found using flyctl to be difficult b/c I don’t have 100s of cryptic commands and switches memorized and I don’t even have the right vocabulary yet to ask good questions. So I prefer the web interface for [fly.io](http://fly.io) if possible. If not then I will have to do it via the flyctl. Thanks in advance for any / all suggestions as I am totally lost. ---
**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\ **Post date:** [December 10, 2024, 4:53pm UTC](https://community.fly.io/t/staging-production-help/22899/3 "2024-12-10T16:53:44Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.