-----BEGIN PGP SIGNED MESSAGE-----
On 02.10.2006 05:33, * Ryan Schmidt wrote:
> 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.
Well what I try to build here is maybe best described as mixture of a
webhosting environment and project collaboration à la SourceForge.
For some projects there is only a single webdesigner, for some others
there will be maybe upto five collaborators.
All together maybe a dozen projects and upto 50 deveopers/designers.
80% to 90% of them are connecting from outside the LAN, so Samba is not
Around 40% are on Macs, the rest on Windows and occasional a Linux/UNIX
So I am left with WebDAv over SSL/TLS. Wich I need anyway for the SVN
access (and which i got working).
>> 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 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.
Another way would maybe work like this:
Let the users connect over insecure but proven FTP to their working copy
folders and do the SVN related tasks (Import/Checkout/Commit etc.) with
some web-based tools.
Has anybody heard, read, used or was thinking about solutions like this?
Any thought will be greatly apreciated :-)
Greetings from Switzerland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Oct 2 22:12:05 2006