awesome-compose VS solar-monitoring-stack

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/

I've got an example you can use with influxdb V2 and grafana, as a starting point. https://github.com/jsloane/solar-monitoring-stack

If you're a fan of docker, take a look at my setup here https://github.com/jsloane/solar-monitoring-stack