Matt,
The route I went, and this may help you, I setup a Directory for
development and one for production.
The production servers I checked out a working copy of the production folder
where only the administrator has the ability to commit to. Then I set up a
crontab job to do a svn up every half hour this will keep the Production
servers current.
I did the same with the development servers but the developers have commit
ability and the crontab is set to every min. this allows developers more
"Real Time" web developing environment and prevents users from updating the
Production systems.
Hope this helps.
Scott
-----Original Message-----
From: matt farey [mailto:matt.farey@gmail.com]
Sent: Wednesday, March 14, 2007 7:10 AM
To: users@subversion.tigris.org
Subject: code release cycle under svn
Hiya,
I've come late to SVN use, so I apologise if this question gives you a bored
sinking feeling!
A web dev project is getting increasingly complex, I would like to know how
to stage the release of the code to the web server, so that each month I can
use SVN to push a working set of files to the server delivering a
predictable code release cycle to the client.
I realise I could just commit (with note "release 1.0" in the log) from my
working copy, then from the server check out a particular revision into the
web root for that app, but was wondering if I could get some thoughts from
more experienced users. In major opensource releases I notice there are
often multiple directories corresponding to each new release, I like this
structure.
The project as a whole is only a few MB so I'm not too concerned about HD
space, what most concerns me is transparency, - I am still at the newbie -
"black box awe" stage of SVN use!
At the moment the repo is organised like so:
www.webserver.com/www/trunk/private/
www.webserver.com/www/trunk/public/
where
www.webserver.com/www/trunk/
corresponds to the web doc root for the vhost concerned.
I realise this structure might have to change!
matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 14 21:55:38 2007