awesome-compose VS dockerfiles

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/

https://blog.jessfraz.com/post/docker-containers-on-the-desk... is the one I remember, a bit old but still useful to see how she does it.

Seems super painful and indirected for a nebulous gain to me, but find your joy however you want I guess

Jess does some awesome stuff and this is literally what you asked for. hollywood

mildly relevant https://blog.jessfraz.com/post/docker-containers-on-the-desktop/

Some of my day-to-day software.

After knowing that saved Chrome passwords and cookies in Linux are not protected against malicious dependencies in our development environment or other apps in our system, I decided to run my core apps in Docker containers, where their data is not accessible without sudo, and a personal understanding of where stuff is being saved.

These docker containers are also an improved version of https://github.com/jessfraz/dockerfiles/

Contrary to the project above, docker-workspaces runs Chrome in a sandbox, encrypts keys with the help of an also dockerized gnome-keychain, and works in tandem with pulseaudio, so you can use wired headphones (i still need to add some dependencies for it to work with bluetooth headphones).

Thank you. As someone who uses containers a lot (even to run local programs, shout out to https://blog.jessfraz.com/post/docker-containers-on-the-desk...) this makes some sense to me.

I'm a little way into the Nix Pills document (https://nixos.org/guides/nix-pills/why-you-should-give-it-a-...) which seems to start the explanation from a place where I can understand.