apparently building complex configuration management in Bash is "cursed"
and a pile of curses is witchcraft
so I guess I'm a devops witch then
anyway today's cursed activity is extending my Bash configuration management system, Babashka, to support a variable file, that can be used in various build thingies.
since right now I'm using a bad hack to find absolute paths, which is clearly Not Ideal.
The real question is, do I use a .ini parser, or, just have something that sources a file, or what.
I guess we'll find out.
@aurynn I've...been a big fan of sourcing things, because that allows another layer of abstraction by running things instead of just k/v if you really need it :P
@arrjay yeah but look at this ini-file parser in Bash that I found:https://github.com/egberts/bash-ini-file
a tiny corner of the internet. live más.