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

Re: Subversion and samba

From: Ryan Schmidt <subversion-2008a_at_ryandesign.com>
Date: Fri, 14 Mar 2008 14:39:00 -0500

On Mar 14, 2008, at 08:41, Troy Bull wrote:

> On Mar 14, 2008, at 05:28, Ryan Schmidt wrote:
>> On Mar 14, 2008, at 05:10, <nicklist_at_planet.nl>
>> <nicklist_at_planet.nl> wrote:
>>> On Mar 14, 2008, at 04:43, Kota, Sreenivasa ShravanaKumar wrote:
>>>> I have a subversion working copy in unix. I have configured
>>>> samba on my unix box so that I can access the working copy from
>>>> windows. [snip]
>>> First thing, don't share working copies between OS's. Check out a
>>> local working copy, and synchronize them with svn up.
>> Sure, where possible, that's the best idea. Sometimes, however, it's
>> nice to share working copies. We did this in the web design shop
>> where I worked. There was one LAMP server (Linux/Apache/MySQL/PHP)
>> and each developer had his or her working copies under /home/
>> <username>/public_html, and they accessed this using Samba from their
>> Windows workstations and used TortoiseSVN to checkout, update,
>> commit, etc. It can work.
> Why bother? Why not just check out a working copy on the windows
> box? I mean you could dig the grand canyon with a teaspoon, but why?

Because obviously we preferred it to the alternative.

It was a small web site programming shop. The entire company
consisted of the two founders, a consultant friend of theirs, a
secretary, and ten web site programmers. No IT staff, no system
administrators. One of the other programmers and I became the de-
facto sysadmins, because we liked that kind of stuff. And we
preferred to spend our time making sure our one Linux server had the
correct mix of Apache, PHP, PEAR modules, MySQL, ImageMagick,
Graphviz and the various other tools the sites needed, rather than
trying to keep all these things updated and working properly on each
of our ten programmers' workstations. The other programmers did not
like IT stuff and weren't going to be forced to learn how to do that
on their own systems. That's not what they were hired for. They were
hired to program web sites. Also, our sites were hosted on Linux on
the production side, so we wanted them hosted on Linux on the
development side too. And we certainly didn't want to invest a whole
lot of effort into making our sites work on Windows.

Before I helped introduce Subversion to the shop, everyone was
writing their files directly to a single Samba share, routinely
clobbering each others' work. Quite a mess. Switching to Subversion
and writing to individual working copies in home directories mounted
via Samba was a definite improvement.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-14 20:39:54 CET

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.