M, I personally have implemented deployments based on Capistrano for unnamable clients who had the largest government in the western hemisphere as their client; the site in question had millions of hits per week; and was hosted on 140 VPS servers on EC2.
In Europe I have consulted with a business social networking site (not linked.in) with more than 300 servers, and a dedicated deployment team. On the other side of the scale there are individuals using Capistrano to deploy individual, small projects to VPS slices, or smaller. EngineYard famously was built around Capistrano, I'm lead to believe lately they're on something custom-built for their own needs; since Cap was starting to hold them back, their business however is predominantly server provisioning these days. Only you can answer if Capistrano is right for you, and only by trying it out. It's well documented, in my opinion but being rather specialist software it's quite easy to be lacking knowledge not directly related to Capistrano that's actually essential to use it. We (or rather I personally) intentionally avoid documenting these things (Git, SSH keys, user management, umasks) etc because they do fall outside the remit of a deployment tool, these are often the first stumbling blocks for beginners, don't expect to find answers to these questions in our wiki. - Lee -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
