Foy, Sean wrote:
>> 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.
>
Having those .svn directories on the live server also offers you the
great benefit of using Subversion's highly-efficient update mechanism to
push changes to your server. Only lines which have changed need to be
pushed and it happens very quickly, because those working copies keep
track of when the last update happened, and what the files looked like,
so only the changes themselves need to be updated. Best deployment
strategy I've ever used.
There are also those times when I'm away from a dev box and I need to
make an emergency change on the production server. In that case I just
make the change and commit it from the production server. Of course that
should be avoided whenever possible but when it is necessary, it's nice
to know that Subversion will let me easily see what changes I made and
ensure that I don't forget to commit them back to the repo, to prevent
them from being lost next time a dev change is made.
toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 27 16:53:25 2006