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…

[image] RGJ: Because of the Ember asset pipeline. This one: GitHub - ember-engines/ember-asset-loader: Asset loading support for Ember applications ? [image] 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 …

[image] 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/orc…

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…

[image] 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 time…

[image] 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 upgrad…

[image] 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.

[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? [image] featheredtoast: That was a note for why the compose…

[image] 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?

Discourse peut-il envoyer fréquemment des images Docker qui n'ont pas besoin d'être initialisées ?

Dev

featheredtoast (Jeff Wong) Juillet 8, 2025, 4:47 209

C’était une note expliquant pourquoi l’exemple de composition que j’ai posté n’utilisait pas l’image PG générique.

Sujet		Réponses	Vues
Using a launcher built docker image in docker-compose Development	30	7920	Septembre 27, 2024
Container restart - discourse tries to reinstall Self-hosting unsupported-install	24	2961	Juillet 30, 2020
Installing on Kubernetes Self-hosting unsupported-install	55	25057	Février 6, 2026
Community supported official docker image Development	35	8662	Juillet 22, 2022
Why does Discourse have to use Docker? Self-hosting docker	36	10333	Septembre 29, 2018

Discourse peut-il envoyer fréquemment des images Docker qui n'ont pas besoin d'être initialisées ?

Sujets connexes