awesome-compose VS administrative-scripting-with-julia

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 appreciate the "Why You Shouldn't Use Julia for Administrative Scripts" section[0] which asked exactly the questions I would have asked.

The choice of (non-Bash) language to write command line utilities is in a bit of odd spot right now. Python is basically almost everywhere installed but the dependency on runtime + venv oddities bring their own set of problems. Java has the same runtime need issues though things might improve with initiatives regarding native binary compilation (though including the runtime may not produce exactly lightweight executables). Perl used to be a hot favorite in this space but I don't think lot of people are writing new stuff in Perl even though it is still present by default almost everywhere. Go is almost perfect here except I don't want to deal with 3x the boilerplate. Personally I think Rust isn't a bad choice (libraries like clap hugely reduce the boilerplate) but the learning curve makes it a harder sell (even though for basic utilities, I don't think there would be too much wrestling with the borrow checker). Another choice that comes to mind is Nim; I think it is very well positioned except a lot of people don't know even about it so its a hard sell + even among those who know, everyone is looking at everyone else to take the initiative to adopt it in a corporate environment at a non-trivial scale.

[0]: https://github.com/ninjaaron/administrative-scripting-with-j...

My question is actually not what everyone uses, but what is best suited for the task. Those two things are, of course, almost always different, because the average person is anything but smart. Here you see that Julia is indeed better suited for handling data than Bash: https://github.com/ninjaaron/administrative-scripting-with-julia And here you see that Lisp will be the best scripting language for certain persons: https://quotepark.com/quotes/1879617-larry-wall-is-lisp-a-candidate-for-a-scripting-language-whil/ Obviously, if you don't have in-depth experience with both languages, you don't have to answer my question.