Glad to see some more effort going into deployment tooling. I think the main goal of reinventing such tools in different languages is to get rid of the need of having dependencies outside of the current project's platform, which makes sense, for me at least.
Shameless plug: I'm the author of Flightplan[1], a library which provides a simple, yet powerful interface to execute sequences of shell commands on local and remote host(s).
I'm a huge fan of Flightplan. I used it extensively at a past job and added it into our default stack. Every site we worked with (60+ at the time I left) was using Flightplan for deployment.
For Less and Sass, it's not very annoying because you don't have to write a lot of ruby code. But writting a complete deployment script if you don't know ruby is very hard... I love to be able to use my favorite JS modules in my deploy script, that's why I wrote Shipit.
I am starting to see the light on all this tooling madness. It does not matter: languages and their ecosystems are powerful enough for any project to build their own tools. Projects are fond of their tools, so they give them fancy names and logos, and release them in hopes they are useful to somebody.
It leverages 'orchestrate' (which is what gulp uses) to do deploys across a variety of hosts, keeping the old versions around should you need to switch back easily.
You can do most of your Ansible work without needing to touch Python. I'm a Python programmer, and I've never needed to touch Python (other than running Ansible, which is a Python program) with respect to an Ansible setup.
Shipit can be an Ansible replacement, but there is no command abstraction to Shipit. Shipit is designed to quickly deploy a project on a set of servers not to configure an entire server.
Sorry, I meant Python. I am familar with Algol syntax based languages and prefer C/C++/ObjectC/C#/Java/PHP/JS/Go/Rust/Lua/Basic/Pascal/Ada/Smalltalk/Scheme over Python/Ruby/Haskel.
What does Algol syntax have to do with that? Several of the first set of languages you list are not Algol-based, while two of the last three are Algol-syntax-based.
They used in to deploy projects internally, same for Le Monde. Shipit is not designed to Shipit projects over a lot of servers. It's designed to Shipit small projects or even to ship code on hardware (like raspberry).
Would be my guess too, but other than a single PR from one of the core devs I can't find any connection between the projects. Is there any source for this?
Shipit is an automation and deployment tool, git hook is just a hook on a git command. You can't run a command on 10 servers in parallel using git hook post-receive.
> Shipit was built to be a Capistrano alternative for people who don't know ruby, or who experienced some issues with it. If you want to write tasks in JavaScript and enjoy the node ecosystem, Shipit is also for you.
Shameless plug: I'm the author of Flightplan[1], a library which provides a simple, yet powerful interface to execute sequences of shell commands on local and remote host(s).
[1] https://github.com/pstadler/flightplan