You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Daragh Fitzpatrick <Da...@UChicago.edu> on 2004/05/17 16:34:24 UTC
SVN Push and deployment
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
Re: SVN Push and deployment
Posted by Toby Johnson <to...@etjohnson.us>.
Daragh Fitzpatrick wrote:
>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)
>
>
>
Not sure what you're getting at with this last part, but are you aware
of the "svn:externals" property? It's "almost" a symbolic link, in that
it lets you point to arbitrary external directories or files which
should always be included in a "checkout" or "export". This lets you,
for example, build a sort of "deployment" file structure which looks
different than the "development" file structure.
If what you're looking for is "shared" projects a la Visual SourceSafe,
I certainly hope Subversion never incorporates this "feature"!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVN Push and deployment
Posted by Gerald Richter <ri...@ecos.de>.
Hi,
you can use SVN::Push to push content from one repository to another. I have
written SVN::Push, because we have one internal server which holds our
development repository and one external server which is used for software
deployment. While the internal repository contains the full history, the
external server only contains the releases, without the need to publish all
changes.
Gerald
Daragh Fitzpatrick wrote:
> 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
> --------------------------------------------------------------------
---------------------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
IT-Securitylösungen * Webapplikationen mit Apache/Perl/mod_perl/Embperl
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 939-122
WWW: http://www.ecos.de/ Fax: +49 6133 939-333
---------------------------------------------------------------------------
Besuchen Sie uns auf der KOMCOM 2004 in Mannheim
25. bis 27. Mai 2004 Stand K11a www.komcom.de
ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
---------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org