There is this open issue (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, dock…

[이미지] RGJ: Because of the Ember asset pipeline. This one: GitHub - ember-engines/ember-asset-loader: Asset loading support for Ember applications · GitHub ? [이미지] RGJ: Which would be a mess as well, because you don’t want to have those deps externally. Why not though?

Plugins can be processed on the fly, this is also done when upgrading a plugin. With a bit of magic you can also had a new plugin to a running instance without rebuilding the container. So mounting a plugin volume to a container should be possible (with a bunch of changes). The major problem I see …

[이미지] elmuerte: If Discourse actually came from a pre-build image you cannot change those files. So upgrading with zero/little downtime will probably require quite some work. This is something I don’t grasp (probably missing context in terms of Ruby…). In general with docker/containers/orche…

Yes, but that’s not how it currently works, so that’s the part that needs work. How are you going to do this from within the Discourse admin interface. How are you doing to scale down the blue container while spinning up the green container (systems don’t have infinite resources, so before starting …

Plugins and custom images still need to be built, but for vanilla building for compose is becoming within reach these days - I’ve made a little proof of concept experiment here for anyone curious. Obviously, since these are all my repos (not Discourse’s™) this is not anything Official, so YMMV, and…

[이미지] elmuerte: Yes, but that’s not how it currently works, so that’s the part that needs work. How are you going to do this from within the Discourse admin interface. Eh… this is I think the crucial difference and this “update from the admin interface” is somewhat of a reminder of old times,…

[이미지] wojtek: this “update from the admin interface” is somewhat of a reminder of old times, when you only had “web hosting” with php interpreter so everything was build around that notion. And I think this carried over to how Discourse work and is expected to be managed. This “admin upgrade …

[이미지] wojtek: discourse could provide such pre-build image That was a note for why the compose sample I posted wasn’t using the generic PG image.

[이미지] merefield: This “admin upgrade interface” is a plugin (called “docker manager”). You don’t need to include it if you have another way of doing online updates. Hmm… but wouldn’t you say this makes other ways more complex? [이미지] featheredtoast: That was a note for why the compose sam…

[이미지] wojtek: Hmm… but wouldn’t you say this makes other ways more complex? As a docker guru this should all be very easy for you?

Can Discourse ship frequent Docker images that do not need to be bootstrapped?

개발

featheredtoast (Jeff Wong) 7월 8, 2025, 4:47오후 209

제가 올린 compose 샘플에서 범용 PG 이미지를 사용하지 않은 이유에 대한 참고 사항이었습니다.

글		댓글	조회수
Using a launcher built docker image in docker-compose Development	30	8247	9월 27, 2024
Container restart - discourse tries to reinstall Self-hosting unsupported-install	22	3179	7월 30, 2020
Installing on Kubernetes Self-hosting unsupported-install	56	25958	6월 9, 2026
Is Docker image discourse/discourse considered safe and production-ready? Self-hosting hosting	30	3206	5월 26, 2026
Community supported official docker image Development	35	8902	7월 22, 2022

Can Discourse ship frequent Docker images that do not need to be bootstrapped?

Related topics