yaml as opposed to just writing a sh script and run it via https://github.com/rollcat/judo for example.
yaml as opposed to just writing a sh script and run it via https://github.com/rollcat/judo for example.
yaml as opposed to just writing a sh script.
] is extra\n\n\n if [ -n "${NS1}" ] && ! grep -q "nameserver ${NS1}" "${RESOLVCONF}" ]; then\n] is extra
if [ -n "${NS1}" ] && ! grep -q "nameserver ${NS1}" "${RESOLVCONF}" ]; then
] is extra\n\n\n if [ -n "${NS1}" ] && ! grep -q "nameserver ${NS1}" "${RESOLVCONF}" ]; then\nYes technically you can just write shell scripts, scp ‘em across, ssh back in and run them in some way.
But that’s not the point 🤗
Yes technically you can just write shell scripts, scp ‘em across, ssh back in and run them in some way.
But that’s not the point 🤗
judo, not ssh, but if man if yaml is your thing, just do yaml.
judo, not ssh, but if man if yaml is your thing, just do yaml.
judo doesn't do what shops does, rset is closer, but a bit more complicated/feature-rich(er).
judo doesn't do what shops does, rset is closer, but a bit more complicated/feature-rich(er).
shops. Maybe this helps highlight the differences between shops and judo, it's not about just running a "whole" shell script.
shops. Maybe this helps highlight the differences between shops and judo, it's not about just running a "whole" shell script.
sh script, what am I missing?
sh script, what am I missing?
shops as an "orchestrator".
shops as an "orchestrator".
shops is an orchestrator for a custom language you defined in yaml which runs sh functions, and judo is an orchestrator for plain sh scripts.
shops is an orchestrator for a custom language you defined in yaml which runs sh functions, and judo is an orchestrator for plain sh scripts.
shops is an orchestrator for a custom language you defined in yaml which runs some sh functions, and judo is an orchestrator for plain sh scripts.