On Fri, Jul 11, 2008 at 9:59 PM, Mark Reibert <svn_at_reibert.com> wrote:
> On Fri, 2008-07-11 at 13:57 +0100, Greg Thomas wrote:
> > On Fri, 11 Jul 2008 05:45:06 -0700, "Waynn Lue" <waynnlue_at_gmail.com>
> > wrote:
> > >I'm using svn export to update a production website as certain users
> > >changes. I pass the --force flag to clobber existing files, but I
> > >that if I do svn delete, that change isn't reflected in production.
> > Make you web site a working copy; a "svn update" will then ensure
> > files are appropriately deleted.
> If you do not want all the .svn directories on your web server you can
> use svn export along with rsync. Something like:
> svn export $REPO_URL /tmp/stage
> rsync -aHS --delete /tmp/stage/ $DOCUMENT_ROOT
Ah, that makes sense. Yeah, I was using svn update before, but didn't want
to export .svn directories so went to svn export, but found this new
problem. I've since configured Apache not to allow .svn dirs to be browsed,
so maybe I should revisit the svn checkout/update solution.
Thanks for all the help!
Received on 2008-07-12 11:48:42 CEST