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

RE: Post Commit Working Copy Update - windows

From: Marc <subscriptions_at_advantex.net>
Date: 2006-09-23 02:06:52 CEST

>
> If I understand your situation right, you've already
> got a WC on the server. Sounds like a 1-liner to me:
>
> post-commit.bat:
> c:\progra~1\subversion\bin\svn.exe update
> full_path_to_working_copy
>
> Obviously if you have multiple projects in the
> repository, you'd only want to update the WC when a
> commit happens for that specific project, so some extra
> checks would be needed to test the path(s) committed.

It's working! I can check out a working copy to my laptop from my server
3000 miles away. Make a change, add a file, etc. When I commit, it goes
back into the repository AND updates the development website, which is
simply a working copy that is on the same machine as the repository, again,
3000 miles away. I can then check out the trunk manually to the live
website on that same machine, when the development website is confirmed
working.

Here's my next question... Is it truly unsafe to have OTHER files show up in
on the development and live sites, placed there by the content management
system code that IS in the repository? The CMS is in the repository, the
files uploaded BY the CMS when it's in use are not, nor will they ever be.
What are the pitfalls of having "extra" files in the development and live
website directories, that are not under version control? What is the
likelyhood of a real disaster, and what types of things could cause a
disaster to occur?

Thanks for your time... I am so excited that this seems to be so rock solid
so far...

marc

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 23 02:07:33 2006

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