[Top][All Lists]

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

[Gnumed-devel] Re: Bootstrapping for production -- user accounts

From: Jim Busser
Subject: [Gnumed-devel] Re: Bootstrapping for production -- user accounts
Date: Tue, 04 Aug 2009 14:58:23 -0700

On 25-Jul-09, at 3:51 PM, Jim Busser wrote:

But as we saw from my last few emails, disabling the demo user accounts and demo patients and data takes a lot of steps prone to human error:

- bootstrap-test_data.conf (in bootstrap-latest.conf)
- several Data and Accounts .sql lines yet to be confirmed in bootstrap-monolithic-core

also in bootstrap-monolithic-core to disable or factoring out

superuser schema = $superuser schema$

This recent thread intersects the new one about CCHIT...

Even without considering the specifics of CCHIT, it remains IMO very desirable to easily bootstrap a "clean" GNUmed *without* test data (some of which, like demo patient Horst) does not even live in /test-data.

Despite that it is true that an administrator could 'delete" such test patients, there is a possibility that post-installation there is some need to pore over the data (including deletions) and  in such an instance, the lack of test data to confuse things would be a benefit.

I would make a strong vote to make a "clean" GNUmed part of 0.6.

When time permits to refactor the bootstrap, what about
- refactoring all of the test data import into a single bootstrap script file
- making the import of the test data *optionally* callable either through parameter or through an interactive command line question?
- and building into the main bootstrap script a command-line prompt 

reply via email to

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