30
top 18 comments
sorted by: hot top controversial new old
[-] ma1w4re@lemm.ee 10 points 2 months ago

Looks like another make. What are the differences though...

[-] Ephera@lemmy.ml 5 points 2 months ago* (last edited 2 months ago)

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.

[-] GammaGames@beehaw.org 3 points 2 months ago* (last edited 2 months ago)

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

[-] ma1w4re@lemm.ee 2 points 2 months ago

I'm just gonna put this little bad boy into my stash of interesting libraries.... Here we go. 😖

[-] GammaGames@beehaw.org 2 points 2 months ago
[-] ma1w4re@lemm.ee 3 points 2 months ago

aight, why not, might as well try it out :D

[-] GammaGames@beehaw.org 2 points 2 months ago

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

[-] ma1w4re@lemm.ee 2 points 2 months ago

I see, I see.

[-] GammaGames@beehaw.org 4 points 2 months ago

Discovered just yesterday, my life is easier

[-] Xirup@yiffit.net 2 points 2 months ago

This looks awesome to use with Qemu, thanks.

[-] GammaGames@beehaw.org 1 points 2 months ago

Spreading the good word 🙌

[-] lambda@programming.dev 2 points 2 months ago
[-] Kache@lemm.ee 2 points 1 month ago* (last edited 1 month ago)

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 1 points 1 month ago

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!

[-] Kache@lemm.ee 1 points 1 month ago* (last edited 1 month ago)

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

[-] GammaGames@beehaw.org 1 points 1 month ago

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

[-] Kache@lemm.ee 1 points 1 month ago

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

[-] GammaGames@beehaw.org 1 points 1 month ago* (last edited 1 month 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!

this post was submitted on 26 Sep 2024
30 points (96.9% liked)

Programmer Humor

19623 readers
1 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS