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

Re: Updating to repository, Not to SITE

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2005-12-08 19:40:02 CET

On 12/8/05, King, Rogie <RoKing@carroll.edu> wrote:
> That definitely may be the case. What is the concept of a working copy?
> How do they work? About 4 days ago, before all the crap hit the fan, we
> could do an svn-commit to the repository. If I committed an image to
> the repo, then that image would also show up on our webserver. How is a
> setup like that achieved? I would assume that there is some sort of
> mapping from the repo to the server html files.

It sounds like there was a hook script that was either copying your
committed files to the web server, or running an export/update out to
a working copy that resides on the working copy (subtle difference).
Any mapping from the website directly to subversion would involve some
major hijinks, and would be a nightmare for performance, so that
probably wasn't in place.

You already have a working copy, it's where you do your edits and
where you commit from. Have you read the book yet?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 8 21:41:50 2005

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