cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kim Toms <>
Subject Re: deploying to separate environments using different database servers
Date Tue, 21 Jun 2005 23:24:39 GMT
I was wondering something similiar; I have a system where database servers 
are deployed, and I'd like to pull reports off of them. I have a list of 
database servers in a local database, do I have to manually edit the 
cocoon.xconf file as I deploy each new server?

On 6/21/05, Lars Huttar <> wrote:
> Dear Cocoon-based webapp developers,
> I would be interested to hear how others have handled this issue.
> You have Cocoon applications whose source code is stored in a
> repository. You want to be able to install them on multiple development
> machines (on each developer's desktop), on test servers, and on
> production servers.
> The environments (dev, test, production) use separate database servers
> as well as separate web servers.
> But when you checkout the source code from the repository onto various
> web servers, they're all pointing to the same database server, because
> they all have the same datasources defined in cocoon.xconf.
> You could then go in and modify cocoon.xconf separately for each
> environment, but that could get to be a lot of time-consuming and
> error-prone work. (We currently have 38 datasources defined for all our
> applications! Maybe not all of them are still used, but most are, I
> believe.)
> How do you automate this task?
> I'm trying to think of some way to set one global variable that points
> to a dev, test, or production database server, so that code only needs
> to be changed in one place... and preferably not every time datasources
> are added or changed. Maybe it should be done by defining an XML entity?
> Thanks for any responses.
> Lars
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message