Programmer Humor

hideshow 4 child comments

[–] Ephera@lemmy.ml 5 points 2 years ago* (2 children)

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.

hideshow 4 child comments

parent

[–] GammaGames@beehaw.org [S] 3 points 2 years ago* (1 child)

Yes! It reminds me a bit of python’s click library but for bash

parent

[+] ma1w4re@lemm.ee 2 points 2 years ago* (last edited 1 year ago) (1 child)

[deleted]

parent

[–] GammaGames@beehaw.org [S] 2 points 2 years ago

⭐️

parent

[+] ma1w4re@lemm.ee 3 points 2 years ago* (last edited 1 year ago)

[deleted]

parent

[–] GammaGames@beehaw.org [S] 2 points 2 years ago (1 child)

It’s pretty much just make, but I find it easier to work with

parent

[+] ma1w4re@lemm.ee 2 points 2 years ago* (last edited 1 year ago)

[deleted]

parent

[–] GammaGames@beehaw.org [S] 3 points 2 years ago (2 children)

Discovered just yesterday, my life is easier

hideshow 4 child comments

[–] Xirup@yiffit.net 2 points 2 years ago (1 child)

This looks awesome to use with Qemu, thanks.

parent

[–] GammaGames@beehaw.org [S] 1 point 2 years ago

Spreading the good word 🙌

parent

[–] lambda@programming.dev 2 points 2 years ago

Neat.

parent

[–] Kache@lemm.ee 2 points 2 years ago* (1 child)

I've often been able to alias drun='docker compose run --rm --build' and simplify down to:

drun test

Should be able to encode all those wayward args into docker-compose.yml or Dockerfile and only use vanilla docker commands -- that's the whole point of containerization

[–] GammaGames@beehaw.org [S] 1 point 2 years ago (1 child)

The 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!

parent

[–] Kache@lemm.ee 1 point 2 years ago* (last edited 2 years ago) (1 child)

Simpler to keep everything in one compose file if you can, under a test service that doesn't build unless explicitly named

Un-weird that env var and use the normal, boring feature of defining environment under your test service

parent

[–] GammaGames@beehaw.org [S] 1 point 2 years ago (1 child)

The variable is already in the environment, it just doesn’t have a default because it’s required for each container

parent

[–] Kache@lemm.ee 1 point 2 years ago (1 child)

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

parent

[–] GammaGames@beehaw.org [S] 1 point 2 years ago*

Yep, you can also set defaults, required, alternates, etc

This discussion did help me realize that my problem was that I forgot an !override on one of my service’s options. Now it’s just merging the two compose files and setting the profile, thanks for that!