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

Best practices for web developers?

From: pileofrogs <pileofrogs_at_gmail.com>
Date: Tue, 12 May 2009 12:09:23 -0700 (PDT)

Hello, I'm a network admin trying to get some web developers onto
SVN. They're accustomed to editing the files on the server directly
(or nearly so). I've tried showing them SVN and they seem perplexed.
The work flow of checkout->change->checkin->ssh-to-server->checkout-
>build is pretty darn unwieldy. Is there anything approaching a 'best
practice' for web developers using SVN? Here's the thoughts I've had:

1) put a web server on the desktop - this follows the typical software
app developers workflow where you compile and test on your local
machine. Still needs a way to deploy to 'test' and 'live' servers,
but it isn't used as often so it can be a little unwieldy.

2) Use commit hooks to automatically update content on the web server
- simpler, but allows collisions between developers trying to see
effects of code. Needs a way to see different branches/revisions.

3) Instead of commit hooks, make a web page that updates the displayed
content. One more step for developer and more control over branches/
revisions displayed. Can still have collisions on server.

4) Set up multiple web servers. This avoids the collisions, but still
requires a good way to deploy changes.

5) Keep doing it by hand. Just grill the humans to checkout, change,
checkin, ssh, checkout, build...

Thoughts? Advice?



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-12 21:09:58 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.