3 ms·
Goodness, I hope all the people using SVN to deploy are making sure that they're taking care of the .svn directories and the resulting security issues.
by unsane1 16y ago
Goodness, I hope all the people using SVN to deploy are making sure that they're taking care of the .svn directories and the resulting security issues.
- JonnieCache 16y agoI assume they're `svn export`ing rather than `svn checkout`ing.
- unsane1 16y agoYet I see at least one reference to `svn update` I'm scurred.
- gregjor 16y agoRead the whole comment. It's easy to configure Apache or whatever HTTP server you're using to not serve anything in .svn directories. Duh.
- bradleyland 16y agoDon't be afraid, just configure your Apache server correctly and you'll be fine. One-liner if you're already using rewrite: RewriteRule ^(./)?.svn/ - [F,L] If you're not: <Directorymatch "^/./.svn/"> Order deny,allow Deny from all </Directorymatch>
- joeuser12 16y agoThe bigger problem is that a svn update isn't atomic, so you are going to be in an inconsistent state for a while. Capistrano with its atomic symlink switch is a much better approach although you have to watch out for caching issues and clear caches appropriately.