On Oct 1, 2006, at 17:31, Alain Wolf wrote:
> On 01.10.2006 20:52, * Andy Levy wrote:
>> Have every developer capable of running the website/project on their
>> development machine. This may sound odd to you, but it's a better
>> of doing things. IIS comes with WinXP and Win2000 Pro, so
>> this shouldn't be a problem. Each developer works from his/her own
>> working copy, and when happy with their work, checks everything
>> they've done into the repository. Your hook script then updates the
>> server for everyone to see.
> I had that before and i wanted to get rid of it for various reasons.
> Apache/PHP/MySQL on every workstation (Windows/Mac/Linux) ...
We also wanted to avoid this.
> (agreed we could skip the MySQL part)
> But still i ran in the same conceptual problems as Adam described and
> presumably some others too.
> Since then I think about giving each developer/webdesigner his own
> on the development server with Apache virtual hosting.
> So for a client would have his personal *working copy* on a webdav-
> and later do commits to the dav-svn share.
> All this using TotoiseSVN as the svn client. And maybe Novell NetDrive
> if needed.
> Has this been done? Or similar?
Yes, we did this in the company where I worked. Linux server serving
home directories via Samba, clients accessing via Windows XP, server
serving up the contents of each user's public_html directory with
Apache 2. The many .svn directories in our many working copies for
our many projects seem to have been a bit much for our development
server. I think the problem was probably insufficient disk cache, but
getting sufficient disk cache would probably have been impossible. It
will depend on how big your projects are, how many of them there are,
how many developers you have, and how many working copies each
developer regularly uses.
> I tried and failed with obscure 404 errors from Apache when
> tries to move the .svn folder from ./temp in its target destination
> during checkout.
It was never a problem for our Windows XP users with TortoiseSVN.
From my Mac, I was never able to use the svn command-line client to
manipulate the working copies on the mounted Samba volume because of
weird errors like this. I was the only Mac user in our office and I
was content to ssh into the Linux server and use the command-line
client from there so I didn't investigate the problem further.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Oct 2 05:34:24 2006