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

Re: suggestions for Best Practices for SVN with staging->development website environment?

From: Shawn Harrison <harrison_at_tbc.net>
Date: 2004-12-15 17:47:48 CET

Subversion Newbie wrote:
> The thing is, we want to have a "staging" (or "development")
> website and a "production" website. Ideally, after they're
> satisfied with the way their changes look in the "staging"
> website, users would somehow indicate that those files should be
> propagated to the "production" website. (There would be a
> similar script doing "svn update" under the "production"
> website's DocumentRoot.) I know that this is how one does
> things in a traditional software development environment with
> longer development cycles, but in this case different people
> will be making changes to files all the time, and have to
> incorporate them into the "production" website. We don't want
> users logging in to the server, or set up individual
> "development" environments for each one, or anything like that;
> we want them to check out to their PC (via Tortoise/SVN) and
> edit locally, then commit back.

So, don't auto-update the production server as you do with staging.
Instead, you add a button or a link to the staging server page footer to
"put this version of the page in Production". The button (link) has
hidden variables (query args) for the path and revision number of the
page. The button (link) triggers a script that updates that file and
only that file, to that specific revision, in the production server's
working copy.

Shawn Harrison

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 15 17:49:10 2004

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.