[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: Development testing on Production (?) servers --

From: James Busser
Subject: Re: [Gnumed-devel] Re: Development testing on Production (?) servers -- was 0.3-rc4 released
Date: Mon, 18 Aug 2008 20:24:55 -0700

On 18-Aug-08, at 6:23 PM, Jerzy Luszawski wrote:

Tuesday 19 August 2008 02:53:16 Rogerio Luz napisaƂ(a):
If the DEVEL database will NEVER interfere with the production one (as Karsten suggested) I would think that there would be no problem working with
both on the same live system.

I see no problem.
Create backup (or schema scripts) of current db. (use pgadmin3 or pg_dump)
Create new db with different name.
Restore data from backup or generate schema in the new database. (use psql \i command, pgadmin did not work)
Modify gm-from-cvs.conf adding a profile pointing to the new database.

I just figured to re-unite under this newly named thread a portion of Karsten's recent comment (below). It only makes me wonder if there is additional manual work beyond what Jerzy listed above for example the need to do a global replace on name within the bootstrap scripts - if the text strings happen to permit that to be precisely done without inducing error.

Would there be a problem to use same permissions as would have been used for the production version?

On 17-Aug-08, at 12:11 PM, Karsten Hilbert wrote:
How many gnumed DB can I have on a localhost: ?

As many as you want and your hardware supports.

It is directly supported and very easy to have one database
per version on one machine, eg. v7, v8 and v9. This is done
when upgrading to a new version anyway. This can be used to
keep a "real" patient database and a next-version database
for testing the next version of GNUmed on the same machine.

It is also possible to have several databases of the same
version but that needs manual work: They need to have
different names (for example gnumed_v8_1 and gnumed_v8_2).
One needs to make sure that database permissions,
bootstrapping scripts, config files etc are adjusted to the
corresponding database name appropriately.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]