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

SVN Push and deployment

From: Daragh Fitzpatrick <Daragh_at_UChicago.edu>
Date: 2004-05-17 18:34:24 CEST

Hi,

I'm trying to work out the best way of keeping a multiple environment
scenario straight, and was wondering if SVN Push should be a part of it.

We have the following environments:
. Development
. Test/QA
. Production
. Backup
. Training

I haven't decided yet whether I should have one repository for all
environments or multiple repositories, one for each environment

Basically, it's a deployment issue. I wish to have the developers work in
the development environment (duh), but have an easy way for an administrator
to deploy the files (config, code, documentation, etc.) out to the different
servers - we're lucky it's a web project and nothing has to be built (I.e.,
with makefiles)

I am currently thinking to put everything into one repository (did I mention
we're using TRAC, and it will only work with one repository?), and have the
servers pull the files from the repository for deployment. So, the
production server would pull from the production part, etc.

With multiple repositories, it just seems like it would be more messy, but
more secure. We could live with TRAC not accessing all repositories, and
might even be able to live with checking out of a tag directory and checking
into the next environment, but I'm suspecting this is just reinventing the
wheel..

Has anyone done this? What's the best approach in general?

MANY thanks in advance.

PS On a side-note, it would be fantastic if SVN had a way of symbolically
linking directories so that repository design would be more forgiving (since
easy navigation is an issue)

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick Daragh@UChicago.edu (773) 702-8976

Solutions Architect NSIT Administrative Systems
Renewal Projects and Architecture University of Chicago
--------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 17 18:36:13 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.