A company I worked for used make to execute docker, which felt somewhat odd.
Correct me if I'm wrong, but I always assumed `make` to be one of those build tools that could incrementally build targets based on dependencies.
The arcane and esoteric language that constitutes `make` is almost universally avoided, surely if people need a simple task runner there could be better options?
I use it for executing docker as well, because the docker command is actually about 5 commands with long lists of parameters. But it's just `make docker-stack` for everyone now.
But then the docker command is starting docker and running the same makefile again inside the container, which becomes hellish to reason about. It's probably better to just make a separate script for that instead.
That is odd. Within the docker container, I agree, you probably shouldn't do that. Esp. since Dockerfiles themselves allow you to run a list of shell commands as your entrypoint.
Correct me if I'm wrong, but I always assumed `make` to be one of those build tools that could incrementally build targets based on dependencies.
The arcane and esoteric language that constitutes `make` is almost universally avoided, surely if people need a simple task runner there could be better options?