Good question! The main benefit is you deploy directly from your git-server to your production server, instead of uploading from your own computer. This means a lot faster deploys, especially when your deployments are large or your internet connection is really poor (being able to make deployments quickly while on a 3G connection is awesome). whiskey_disk uses one ssh connection to your server for all work (so less time for spawning ssh connections), and the heavy traffic is not to/from your local machine.

Other benefits of the tool include putting all config files into version control, and a lot less less magic in your deployments.

I'm not a fan of fluxflex and I've discontinued using them. Too much middle-man for my liking. Last Friday I worked through http://cuppster.com/2011/05/12/diy-node-js-server-on-amazon-... , better than http://blog.carbonfive.com/2011/09/01/deploying-node-js-on-a..., in the afternoon and save for a couple of idiot glitches on my part, it works fine. EC2 is a real bitch, for me at least, so I'll stick with Linode for now. With a little elbow grease you'll be able to get it to work with Github as well, but I'm looking forward to using whiskey_disk today.