2 ms·

I hope you don't mind me stealing your comment to plug my side project, Judo. It was created in 2016, out of my frustration with Ansible. Judging by the state o

I hope you don't mind me stealing your comment to plug my side project, Judo. It was created in 2016, out of my frustration with Ansible. Judging by the state of affairs, that motivation continues to be relevant. https://github.com/rollcat/judo https://github.com/rollcat/judo

mdaniel 4y ago
You're welcome to plug it, although the top-level thread is likely where you'll get more of the kind of exposure you're looking for: https://news.ycombinator.com/item?id=31399719 https://news.ycombinator.com/item?id=31399719 https://github.com/rollcat/judo#passing-arguments-to-scripts https://github.com/rollcat/judo#passing-arguments-to-scripts implies that project is for sure not for me, but I wish you all the best with it!
- rollcat 4y ago
  > https://github.com/rollcat/judo#passing-arguments-to-scripts https://github.com/rollcat/judo#passing-arguments-to-scripts implies that project is for sure not for me, but I wish you all the best with it! That's one of the design decisions, there should ideally be only one "obvious" way of achieving a certain goal. Per-invocation parameters can already be passed via environment variables ("-e FOO" to pass from your local environment; "-e BAR=42" to set explicitly); I'm also considering using envdir (or a similar scheme) to set per-host parameters (https://github.com/rollcat/judo/issues/11 https://github.com/rollcat/judo/issues/11). I could allow specifying command line arguments somehow with the -s flag, but that would complicate parsing, quoting/unquoting, etc. I would have to teach the user about quoting rules, and probably shoot myself in the foot at least once in the process. I try to actively avoid creating hard problems by solving an equivalent, easier problem. If this is not clear from the readme, I'll take this as a bug report, and try to improve the readme :)

mdaniel 4y ago

You're welcome to plug it, although the top-level thread is likely where you'll get more of the kind of exposure you're looking for: https://news.ycombinator.com/item?id=31399719 https://news.ycombinator.com/item?id=31399719 https://github.com/rollcat/judo#passing-arguments-to-scripts https://github.com/rollcat/judo#passing-arguments-to-scripts implies that project is for sure not for me, but I wish you all the best with it!

rollcat 4y ago
> https://github.com/rollcat/judo#passing-arguments-to-scripts https://github.com/rollcat/judo#passing-arguments-to-scripts implies that project is for sure not for me, but I wish you all the best with it! That's one of the design decisions, there should ideally be only one "obvious" way of achieving a certain goal. Per-invocation parameters can already be passed via environment variables ("-e FOO" to pass from your local environment; "-e BAR=42" to set explicitly); I'm also considering using envdir (or a similar scheme) to set per-host parameters (https://github.com/rollcat/judo/issues/11 https://github.com/rollcat/judo/issues/11). I could allow specifying command line arguments somehow with the -s flag, but that would complicate parsing, quoting/unquoting, etc. I would have to teach the user about quoting rules, and probably shoot myself in the foot at least once in the process. I try to actively avoid creating hard problems by solving an equivalent, easier problem. If this is not clear from the readme, I'll take this as a bug report, and try to improve the readme :)