[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: .svn directories

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-08-27 23:03:21 CEST

John Locke <mail@freelock.com> writes:

> With your patch, I should be able to do:
>
> 1. Download web site, import into Subversion.
> 2. Check out WC to web server.
> 3. Make my changes.
> 4. Sync WC directly with production server.
>
> And then, after the client makes changes, all I have to do is sync my
> WC with the public site, no more import/export and manual merging!

Wow, you've completely lost me.

I read about your 'pain', and the thought that immediately occurred to
me is: my gosh, why isn't the "live" web site also a working copy?
That would fix all your problems.

For example, http://www.red-bean.com/sussman is my home page, and it's
just an ordinary svn working copy. I make changes in my local working
copy, and when I commit, a post-commit script on the server
automatically runs 'svn up' on the live working copy. Instant publishing.

I don't see how that has anything to do with Kumaran's proposed
feature. The existence of .svn/ directories in a live working copy is
no big deal at all. Just add this to your httpd.conf:

# Disallow browsing of Subversion working copy administrative dirs.
<DirectoryMatch "^/.*/\.svn/">
Order deny,allow
Deny from all
</DirectoryMatch>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 27 23:08:31 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.