Which resources? a docker container is really just a process, so as now, it will use the memory for 2 processes. It will share the docker image, and create a writable layer on top. So the added resource is really just this new layer, but it is really small.
Yes, for that, at first at least, it will be manual.
I really like the documentation and approach from mastodon, and will follow that.
Then, on kubernetes, we can get smarter.
Currently, I clone them on the host, and it works okay-ish. I have still to figure some little quirks.
I’ll try to keep it simple for the docker-compose version, but on kubernetes, again, I think we can be smarter.
But this is outside the scope of the docker image in itself.
Once actually, somebody added that logic in the docker image But I’m not sure I like this logic.
I’m open to propositions of course.
This image will have just rails. NginX will run in a separate container.
About the logs, this is not the responsibility of rails to handle this, rails should log to stdout and docker or whatever container runner will take care of those logs.
Just opened a PR to add the possibility to discourse to log to stdout.
@riking again, the best I can do is to warn the user something like:
/!\ This is not officially supported by discourse, if you don’t know what you are doing, use the launcher instead.
For instance, there is no easy path to upgrade the underlying postgres whereas this is handled gracefully in the launcher.
Use this image at your own risks.
What are the next steps? Can you create the repo that can receive the Dockerfile?
Or what is missing from my side?
Thanks for your help!