> And Sean, just wondering how would you manage your deploy
> with svn export ? If I do a svn export over a current
I was just pointing out that in principle you don't need
the .svn admin directories on your web server, because
they just have SVN metadata and base versions of your
files.
As Ryan points out, you might choose to use a working
copy anyway, which would allow you to use something like
the svn-clean script that comes with Subversion (in contrib)
to remove files that are no longer in HEAD.
Or, you could use "svn ls" and delete files that aren't
listed. Or, you could delete everything on the target
and copy everything.
Personally, I use CruiseControl.NET and NAnt. CC.NET
watches for changes in SVN. It has its own working copy.
Whenever there is a change, CC.NET tells NAnt to compile
our ASP.NET project, test it, and deploy it. NAnt decides
what files need to be updated on the web server, what should
be removed, etc. CC.NET gathers up NAnt's results, summarizes
them, and publishes them to its own web site/RSS feed and
emails certain people about test failures or successful
deployments.
Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 27 15:59:58 2006