Capistrano can be installed anywhere in the project tree, but it will prefer to be in the project root. It will deploy the current Git repository to a server. (including, all the Capistrano files that should be checked in.) you might start a 2nd project with your Capistrano deploy code in, where you refer to the project's repository itself.
Mixing the responsibility of *./lib*/ shouldn't be a problem, since any tools that rely on that, should just ignore files they don't recognise. -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/CAN_%2BVLUa7zk8YZLk2802bxr738qQFxENp_NapZRhifg7-gpn4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
