On Feb 3, 2006, at 23:11, Renaud Waldura wrote:
>>> We're a web development company, so everything in our repository
>>> is a PHP web site. We have one central Linux development server,
>>> and everyone has their own working copies in their public_html
>>> directories in their home directories on this server. They mount
>>> this on their Windows or Mac workstations over Samba. Anyone can
>>> test their working copies through the Linux machine's web
>>> server, and once they're satisfied with their changes, they
>>> check them in.
> How is this done? With a Windows/Mac SVN client? Eg. TortoiseSVN.
> How's that working over SMB?
Yes. The Windows folks (8 developers) are using TortoiseSVN, which
they seem to like just fine. Occasionally I hear the little badge
icons don't show the right thing, but I don't know if that's related
to it being a Samba share or something unrelated. I'm the only Mac
person at the moment, and we have one employee with a Linux desktop,
and both of us use the command line client logged into the Linux
server's shell via SSH. Most of the Windows developers also use the
command line client on the Linux server at one time or another.
For deployment on our production Linux server we have a handy shell
script which goes through an elaborate song and dance routine
involving updating a working copy with the latest tag from our
repository, exporting it to a new directory, and switching the "live"
symlink over to the new export. The Apache document root then points
to (a subdirectory of) the "live" symlink. The fact that we update a
working copy means we can pull only the necessary changes to the
production server (instead of copying the whole site in its entirety)
saving time and bandwidth, and by using a symlink to an export
instead of setting the document root directly to the Subversion
working copy we ensure that the update to the new version occurs
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Feb 4 00:19:51 2006