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

Re: Best practices for getting non-tech folks to use subversion?

From: Phillip Susi <psusi_at_cfl.rr.com>
Date: 2006-02-22 22:43:35 CET

Philip Hallstrom wrote:
> Hmmm. If I read what you're saying right, you mean setup a post-commit
> hook (or whatever it's called) to automatically check out any commits
> made to the vhost, right? The problem I see with that is the designers

You could do that, or have a cron job do an svn update every 5 mins or

> would have to commit all their changes even when just playing around
> with something which could get tedious for them. I'd prefer it if they
> could muck around for a bit, get things the way they want them, then
> commit.

They can muck around all they like in their working copy before they
decide to commit. How does that differ from mucking around then
uploading via ftp?

> Good point on the https. For some reason I thought my choices were
> http, svn or svn+ssh. Thanks!
>> I'm no sure what you mean by round trip twice. Small updates and
>> commits should be plenty quick.
> In the case where we have a dev server with the vhost and working
> repository. We use Samba so the user can mount the vhost on their
> desktop. We use TortioseSVN for subversion. When the user tells
> Tortiose to update the working copy, it will communicate with the
> subversion server, downloading any files that need updating and then
> copying them to the samba share. Tortiose thinks it's local, but it's
> really copying them down only to copy them back again.

If you are going to use svn then there is no need for samba; do away
with it. Users can use their local hard drive to hold their working copy.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 22 22:47:50 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.