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

Re: Implementing Subversion!!!

From: Alain Wolf <wolf_at_k18.ch>
Date: 2006-10-02 00:31:22 CEST

Hash: SHA1

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 way
> of doing things. IIS comes with WinXP and Win2000 Pro, so technically
> 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.

Hello list.

I had that before and i wanted to get rid of it for various reasons.
Apache/PHP/MySQL on every workstation (Windows/Mac/Linux) ...

(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 space
on the development server with Apache virtual hosting.

So for a client would have his personal *working copy* on a webdav-share
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?
I tried and failed with obscure 404 errors from Apache when TortoiseSVN
tries to move the .svn folder from ./temp in its target destination
during checkout.

It does not have to be that as described either, I asking here first for
best practices before triying to make things work technically.

Thanks for any advice

Alain Wolf
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 2 00:35:41 2006

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.