alebcay
commented
8 years ago Sorry I haven't been able to get around to this in the past few days. Here are my thoughts:
- I don't have much experience with Vagrant/Ansible, and once tried setting up Puppet, but decided it was way too complicated, and I don't provision machines often, but seeing shell scripts instead of config files with Wick is a happy change. Modularity is probably a good idea from the start - have an extension framework so that people can also add their own modules at some point, perhaps. I'm planning to add Wick a bit later after it matures a bit.
- I don't use much templating in my scripting work at all, so personally, I wouldn't find mo very useful, but I'll definitely add it because I can think of situations where it would be helpful.
- ansi is by far the most useful of the three tools you mentioned (to me, at least). Looking up escape codes is a pain!
I'll get around to adding changes in the next day or two.
fidian
I'm maintaining a Bash-only alternative to Vagrant / Ansible / cdist / Puppet. It's called Wick. It doesn't provision the machines (yet) but if you rsync a folder then you can run a shell command that will provision a machine for you.
I'd be interested in getting your feedback and possibly having it included here. I know that I'll be researching many of the links you have and might split Wick up into modules so others can benefit from my functions more easily. Thanks for making your list; I am finding it very useful.
I've also made other Bash-only tools such as mo (mustache templates written in only Bash) and ansi for ANSI escape sequences such as color codes and cursor control. I don't know if those would be of interest, but they seem to fit your collection of tools.