awesome-compose VS mrsk

examples here: https://github.com/docker/awesome-compose/

Docker compose wraps the app and db in a few lines of config: https://github.com/docker/awesome-compose/tree/master/offici... the extra config is for networking / db connections - you don't get those on Android because you don't run network services on it.

K8s can do the same thing, but has more options.

Simplicity: Docker Compose is easy to use, requiring no extensive DevOps knowledge.

I'm a big fan of people who write guides to help - but to balance this, this can be deployed with a one liner, with NPM, its database and the WP frontend, with one line with docker-compose. It would be quicker to update, faster to boot and use noticeably less resources.   Good work on documenting your OVA conversion though, as that is still useful and can be generalized. :-)

I'm trying to use the react-express-mysql awesome-compose as a framework for setting up multiple react apps that are tied to the same domain. Once dev is complete, I update the Dockerfile for the frontend to add in Nginx and have Nginx serve the frontend so that it is not running using npm start. I additionally am using Nginx Proxy Manager as a reverse proxy to route where I need and manage SSL termination for me.

Take a look at https://github.com/docker/awesome-compose pick your stack and use docker compose up -d

Check out awesome compose there might be overlap projects

Maybe easier to link to a recommended docker compose config that also fails : https://github.com/docker/awesome-compose/tree/master/official-documentation-samples/wordpress/

Here we'll deploy Anycable wih MRSK.

Honestly these days I am leaning towards this approach: https://github.com/mrsked/mrsk/

It's all just docker.

Did you consider MRSK[1], k3s[2], or dokku[3]? They are all significantly simpler to operate than Kubernetes, curious to hear your take.

[1] https://github.com/mrsked/mrsk

https://github.com/mrsked/mrsk/pull/159 Closed PR about --cache-to option in MRSK

Yes, that thing with the setup is misleading in the docs. I'll make a PR now. There's this issue about it: https://github.com/mrsked/mrsk/issues/301

god or bad, dhh is doing noise and people know about rails. just look at there https://github.com/mrsked/mrsk

I don't think there's a writeup out there, but mrsk just uses docker under the hood. So, if you have a CMD in your Dockerfile, it will use that.

If you have an image that can run multiple things, like a rails app that can run the app process for web traffic by default, but it can also run job workers with the right command, you can provide the cmd in the mrsk config. You can see this in the jobs role in the example: https://github.com/mrsked/mrsk#using-different-roles-for-ser....

You may want to checkout MRSK if you are going to be using docker compose in production on a single VPS https://github.com/mrsked/mrsk

"MRSK basically is Capistrano for Containers, without the need to carefully prepare servers in advance" https://github.com/mrsked/mrsk

https://github.com/mrsked/mrsk might be interesting to you.