Looks like another make. What are the differences though…
Here’s their FAQ answer for that: https://just.systems/man/en/what-are-the-idiosyncrasies-of-make-that-just-avoids.html
I imagine, there’s various smaller differences in how the recipes are defined, but yeah, this is the big one.
I find that Just feels a lot like just a collection of script files, with built-in error handling for argument parsing and during execution. And it also offers easier discovery of available tasks and how to use them.
aight, why not, might as well try it out :D
Yes! It reminds me a bit of python’s click library but for bash
I’m just gonna put this little bad boy into my stash of interesting libraries… Here we go. 😖
⭐️
It’s pretty much just make, but I find it easier to work with
I see, I see.
Discovered just yesterday, my life is easier
Neat.
I’ve often been able to
alias drun='docker compose run --rm --build'and simplify down to:drun testShould be able to encode all those wayward args into
docker-compose.ymlorDockerfileand only use vanilla docker commands – that’s the whole point of containerizationThe env file is the weirdest part, the container itself has a required environment variable and if I don’t pass it in command line (only have it in the test compose file) the base compose fails because it has no port.
Most of the other commands are to merge the compose files so I can keep my base compose file clean!
Simpler to keep everything in one compose file if you can, under a
testservice that doesn’t build unless explicitly namedUn-weird that env var and use the normal, boring feature of defining
environmentunder yourtestserviceThe variable is already in the environment, it just doesn’t have a default because it’s required for each container
You can reference envs from the host in docker compose, so code it in instead of manually passing tribal knowledge in: https://stackoverflow.com/a/73826410
