till wrote:
On Thu, Mar 6, 2008 at 2:05 PM, Jim Pingle lists@pingle.org wrote:
(...) The access part is easily solved with a rule in Apache's main config like so:
<DirectoryMatch "^/.*/.svn/"> Order deny,allow Deny from all
</DirectoryMatch>
If you really want to stick with svn do an svn export, not an checkout/update.
Export rids you of the .svn directories etc..
I've hit a couple issues when exporting from a working copy. First, it doesn't copy local-only files such as main.inc.php and db.inc.php. It also doesn't copy ownership/permissions from the working copy that aren't set in svn properties. You also lose the ability to quickly update with "svn update" rather than removing the whole tree and exporting again, or forcing an export and possibly having some inconsistent files.
As part of a deployment procedure, it has its place, but it's still a lot more complex than using a working copy and blocking public access to the .svn directories. It's a lot more convenient that way, even if it does lend itself to foot-shooting from time to time.
Jim
List info: http://lists.roundcube.net/dev/