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

RE: Subversion and the Dynamic Website

From: Marc <subscriptions_at_advantex.net>
Date: 2006-09-20 22:06:53 CEST

Okay, so I've been experimenting... Here's what I have on our remote server:


The contents of "svntest.website.com" and "svntest.website.com.dev" are
exactly the same:


Those two directories represent the virtual web hosts for the
development/staging/qa site, and the live website. The www directory in
each of those two directories is shared via IIS.

The repository is in svntest.website.com.repo.

I imported svntest.website.com.dev into the repository. So now the
repository has the following structure:

-- trunk
---- www
------ index.cfm

I can connect to the repository on the server, remotely
(svn://myserver.site.com/), and I can Checkout the /trunk directory, make
modifications to index.cfm, save, update, and commit.

I'm having trouble understanding the workflow from here, both with creating
the dev site that will be used, and creating the live website checkout or

First... When I edited and saved index.cfm, and then did the recommended
"svn update" and then "svn commit" all went well. From the server site
Tortoise, I can see that the revision number went up. The log file for
index.cfm shows my username as the most recent revision. The repository IS

Now, since the entire contents of the .dev directory was initially imported,
should I delete and recreate svntest.website.com.dev, and then do an svn
checkout, or should I delete it, recreate it, and do an svn export? The end
result I am looking for is that each time the repository gets a commit from
a client, it should immediately write out the changes to the dev site, so
that the changes can be tested right away. This means I'll have to create a
hook after commit, that does either the update or the export.

Then, when the dev site is considered 'up to date', I will deal with
updating the live site...

I saw no way to share the repository file/folder structure 'as' the dev site
directly... I am making the assumption that the dev and live sites both need
to act as one-way (repo --> site) updating working copies... The dev site
updating immediately on each repo commit, the live site being updated only
on demand, after the dev site has been reviewed for bugs.

Is this the proper work flow? (yes, this still does not deal with the
dynamic content being created through the USE of the code... But I'll deal
with that later...)

Am I in the ballpark here, or is this more complex than it needs to be?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 20 22:08:45 2006

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