If you want to deploy it in an environment that is already running some kind of container orchestration it may actually be simpler to just add another container, compared to adding another host service you need to care about.
Sure, you wouldn’t want to install docker, or podman or nomad (+ one of those) or k8s (lol…) to run a redbean. But the other way around might make sense.
Docker is more than just application containerization, it also lets you infra as code to some degree. You can specify where and how files are organised. It turns a git repo into something consistently runnable with the same commands as every other repo you may maintain.
I swear people have forgotten that things can be run directly on OS without any layers in between. They feel naked without docker. 'But mah complexity!' they yell when they see plain old binary nowadays. Grr.
> They feel naked without docker. 'But mah complexity!' they yell when they see plain old binary nowadays. Grr.
That's because they kind of are naked -- containers bring namespace and cgroup based isolation.
If they weren't doing that, then they'd be juggling systemd slices...
If they weren't doing that they'd be setting up per-app users and fussing with ulimit...
And if they weren't doing that, they really would be naked.
I'm very much (as you might be able to tell) pro-containers -- they're a great tool, and they actually do kind of deserve to go most places.
Containers shouldn’t be absolutely everywhere, but they should be the default these days as a layer between the OS and a possibly clueless app developer.
Im pro cgroup isolation but I hate docker. For the first 5 years I used it it definitely caused me more problems than it solved and its design is still bad.
It's fortunate podman exists now coz I was starting to sound like a crackpot.
You have no idea how painful it is to put some static content in a Kubernetes cluster somewhere. With Redbean, you can do it very easily and very resource-effectively.
I also wouldn't utilize it, but perhaps there is a situation where you want redbean for running code on various devices, but maybe in certain limited cases you need to run it in Kubernetes or whatever, in which case this is a useful tool.
My point was that if you needed something like redbean for your architecture because it's flexible and can run on anything, you still might want to run it in a container for some corner-case where running it outside the container isn't possible or easy.
I have a specific use case I'm developing on redbean and I usually need to run it on whatever PC is available at the time, but sometimes a container image running on some orchestrator is necessary because there is no PC available or the user wishes to integrate it into a larger system architecture.
This a very sad situation where someone seems to appreciate your work and would like to do something extra on top of it but completely going against the very principle of that work is based on in the first place.
Technology is not a religion.
When someone uses what you created in a different/unexpected way you anticipated, you know you did something flexible which is useful for a lot of people in a lot of different ways.
