# Best practices for rolling out and maintaining a Glide App

**URL:** <https://community.glideapps.com/t/best-practices-for-rolling-out-and-maintaining-a-glide-app/48264>\
**Category:** Ask for Help\
**Created:** [September 1, 2022, 12:40am UTC](https://community.glideapps.com/t/best-practices-for-rolling-out-and-maintaining-a-glide-app/48264 "2022-09-01T00:40:29Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [September 1, 2022, 2:39am UTC](https://community.glideapps.com/t/best-practices-for-rolling-out-and-maintaining-a-glide-app/48264/6 "2022-09-01T02:39:05Z")

</div>

> [@Jeff\_Hager](#):
>
> If you really wanted, you could duplicate an app, as well as all of the data, and then make your changes to that duplicate copy of the app, but then switching out apps when you are ready for production would involve switching out urls, custom domains, and manually updating data in your duplicated tables so it matches the current live data. It becomes a whole lot of work.

I do this for one of my clients. They insist on being able to test new features in a “staging” app before anything goes live. So I developed and documented my own process for managing this. This is what it looks like:

 ![dev-notes](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/e/7eee74abfd6357822ca4013418175290bf9ddd2b.png)

It’s fiddly, and the switchover process is fully manual. Usually takes me about 30-60 mins to deploy a new “production” version.

---

_[View the full topic](https://community.glideapps.com/t/best-practices-for-rolling-out-and-maintaining-a-glide-app/48264)._