# How Discourse deals with upgrades **URL:** https://meta.discourse.org/t/how-discourse-deals-with-upgrades/140005 **Category:** Support **Created:** [January 29, 2020, 2:08am UTC](https://meta.discourse.org/t/how-discourse-deals-with-upgrades/140005 "2020-01-29T02:08:48Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![Remah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/remah/32/70590_2.png) [@Remah](https://meta.discourse.org/u/Remah) #### Post date: [January 29, 2020, 6:30am UTC](https://meta.discourse.org/t/how-discourse-deals-with-upgrades/140005/3 "2020-01-29T06:30:11Z")
Are asking about how you might be able to create base images and deploy updates? Or do you want to duplicate what Launcher does for a different application? Either way, then there are many topics about the different approaches. Just search for “docker compose” in this forum. But the best topic for you on updating with Discourse Launcher may be this one: > [@Can Discourse ship frequent Docker images that do not need to be bootstrapped?](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205): > > There is this [open issue](https://github.com/discourse/discourse_docker/issues/186) (which I just closed) on Discourse Docker repo asking Discourse should behave like a standard docker image a docker user excepts to be able to run discourse without a special launcher. to define multiple containers (redis, postgres, discourse,..), links and volumes, docker-compose should be used instead. [Docker Compose | Docker Docs](https://docs.docker.com/compose/) The question is somewhat misguided, but I would like to address a broader one of Can Discourse ship frequent Docker images that do … --- _[View the full topic](https://meta.discourse.org/t/how-discourse-deals-with-upgrades/140005)._