Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I use svn update to deploy, but have recently explored Capistrano. I see they support checkout, export, copy, and update+copy, but not just update. Is it frowned upon to use an svn working directory as a deployment directory and why?
one reason is b/c SVN leaves a lot of “.svn” subdirs everywhere, which can be easily exploited to get directory structure and, maybe, any file contents of your project.