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?
views:
16answers:
1
+2
A:
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.
zed_0xff
2010-05-28 20:29:12
Thanks for your thoughts. I did not understand when I first asked that `cap deploy:update` creates a new, empty dir for each release (but always points a symlink named "current" to it), so it must do a checkout. A checkout does not omit the `.svn` dirs, though.
2010-05-29 03:46:09
oh, it creates a new dir each time for the case when something goes wrong with a new release and you could then easily downgrade to a previous release by pointing a 'current' symlink to it
zed_0xff
2010-05-29 06:09:03