Capistrano is a framework, you can choose how to use it. For those of us that choose to use it for provisioning it's actually quite capable, and very low barrier to entry. Unlike Puppet and Chef, which require servers and other resources.
Deprec is a great example of using Capistrano for provisioning, and the project that I referenced earlier https://github.com/donnoman/cap-recipes. There are a number of others if you search. That being said; the developers of Capistrano don't concern themselves with provisioning, nor should they have to. Cap is a great framework, and those of us interested in using it for provisioning can continue developing our own gems for it. Those who want to use it that way can follow our footsteps. Capistrano is "meant" for running tasks via ssh in parallel on servers that match the tasks specifications. It's only coincidence that the itch that it was first created for was deployment of source code. It works well for provisioning, and for capturing institutional knowledge of infrequently and possibly frequently run tasks, that may have nothing to do with deploying source code. I use cap for all of the care of feeding of my application, including proxying rake commands, and one time scripts. I also use it to document our configuration for any sysops person that might come after me. 'desc' rules. 2011/8/11 Manuel Vázquez Acosta <[email protected]> > Capistrano is not meant for that kind of deployment, but only deployment of > some sort of source code. > > I asked this same question months ago, and I was pointed to Puppet, and > Chef. Google for "server instrumentation" puppet and/or chef. > > Best regards, > Manuel. > > > -- * 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
