Parachute: Simple mass web deployment (parachutedrop.com)

I built this system to keep all the users running our new web framework up-to-date with the latest release. It's made being a beta tester better for my clients because I'm able to send out patches at any moment and keep everyone entirely up to date. It also saves hours and hours of my time in trying to manage all the different app deployments I have across multiple client websites. It's like SAAS but done remotely.

So, I decided to built a better interface for it and open it up for the public. The public site didn't take long as all of the ecommerce/account management/subscriptions functionality is built into my flagship product.

Small grammatical nit: setup should be set up.

This looks great! Not all software can be delivered entirely SaaS style, and I've personally ran into hitches with git-based auto-updating of controlled deployments myself. Will take a closer look at this as soon as I have time, thanks! :)

What happens in a scenario where a file that was managed as part of a Parachute deployment is modified directly, and Parachute attempts to deploy a new version of it? I guess I'm asking how potential conflicts are handled. I looked around the help but haven't had a chance to try it out yet.

This looks cool, but doesn't do much to automate my process(es). It doesn't support import from source code control, like Git, and doesn't support SSH/SFTP for secure deployments...