Hi guys. Is it possible to update to newer version without rebuilding the whole thing? I’m thinking of a scenario where two discourse apps are virtually identical and once I have a new image ready - off any one of the two - I could use it to deploy second discourse, having all the config/params fo…

You can build an image, push it to a repo, and then start it up using ./launcher start-cmd app to get the docker command to start up the container (but you’ll substitute your container repo for the local one). And yet, then you need to migrate the database, precompile assets, and so on. If it’s do…

Downtime is not an issue for me. Two apps I think of, would be - virtually identical - but not the same. Two apps would be different sites, meaning, different dbs, volumes, ports, names… but they would have the same - so to speak - base discourse (+ same plugins, same whatever might critical to th…

You can do that as I described. There’s also a new scheme in the works that makes it possible to use a single image and not rebuild. It’s not supported, so you’ll need to search well here or in github.

Hi & thanks. That seems to work, loading a new image and then running rake db:ensure_post_migrations db:migrate seemed to resulted in a fine & healthy new version of container without luncher rebuild - at least for 3.5.0.beta7 to 2025.11.0. That makes me - certainly not just me - thinking…. would i…

이미지를 다시 빌드하지 않고 업그레이드하는 방법?

지원

pfaffman (Jay Pfaffman) 12월 13, 2025, 11:26오전 6

You probably also want to precompile assets

글		댓글	조회수
Building the image without touching the database Self-hosting	13	2372	9월 17, 2023
How do I upgrade Discourse in a multiple container configuration? Self-hosting	2	952	10월 8, 2020
How Discourse deals with upgrades Support	3	1043	1월 29, 2020
Improving pain points on bootstrap and rebuild Development	5	2015	7월 21, 2017
Can you upgrade Discourse seamlessly if there is a breaking db change? Support	12	3046	9월 28, 2018

이미지를 다시 빌드하지 않고 업그레이드하는 방법?

Related topics