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

Re: Subversion, TortoiseSVN, and Windows

From: Jeroen Leenarts <leenarts-jeroen_at_tiscali.nl>
Date: 2004-10-21 18:15:49 CEST

Pat Wenke wrote:

> I am in the process of evaluating SCM software and wondered if someone
> could help me out.
>
> All of our developers code in CFML. The box that hosts our development
> code is a Windows 2000 server that runs both CFMX 6.1 and IIS 5.
>
> The IIS and CF roots both point to the same directory on the server,
> C:\www.
>
> Currently we use no SCM software, so all developers map a drive to
> C:\www on this server, and hence have no "working copy" directories,
> other than their mappings to C:\www itself.
>
> I have configured VSS in the past, where your "working copy" for
> development can be the actual directory that is under source control,
> so I'm
> having a bit of a hard time wrapping my head around the newer SCM
> concepts presented by Subversion and TortoiseSVN.
>
> I can create a repository and connect to it with absolutely no problems.
>
> I can then use TortoiseSVN to connect to the repository and import all
> of our code from C:\www. My questions are as follows:
>
> Can our developers somehow "share" a working copy, so that none of us
> actually have to keep a local working copy?
> Once I commit a changed file to the repository, how do I get the
> updated version back into C:\www so it can be tested?
>
> This particular phrase from the book is what I do not understand:
>
> Now the repository contains this tree of data. Note that the original
> /tmp/project directory is unchanged; Subversion is unaware of it. (In
> fact,
> you can even delete that directory if you wish.) In order to start
> manipulating repository data, you need to create a new "working copy"
> of the
> data, a sort of private workspace. Ask Subversion to "check out" a
> working copy of the repository's trunk directory.
>
> What this tells me is that after I import C:\www into the repository,
> I don't need it anymore. I understand that, and I understand creating
> a working
> copy, perhaps on my local machine, so that I can check out files and
> make changes, and that the changes get committed back to the
> repository. What I
> do not understand is to which directory should I point my IIS and CF
> roots, since C:\www is no longer needed.
>
> I have given all the docs a thorough read and have Googled my eyeballs
> out looking for answers, to no avail.
>
> I am certain it’s just a configuration problem somewhere. Any help is
> greatly appreciated.
>
> Thanks in advance,
>
> Pat Wenke
>

Your statement about not needing the directory is correct when you are
only taking the svn repository in account. All your data is stored
there. But to be able to serve the data contained in your repository,
your web environment still needs a plain file version. Since the
repository is itself a collections database files your web environment
can not read these files. Therefor making the repository contents
available to your web environment is a separate step you need to take.

To automate this a tool like cruiscontrol
*(http://cruisecontrol*.sourceforge.net) could be usefull in a
development environment. Cruisecontrol monitors your repository and runs
an ant or maven script which can deploy the contents of the repository
to your web servers content directory.

Just my 2 cents...

Jeroen Leenarts

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 21 18:16:19 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.