[Top][All Lists]

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

Re: [Gnumed-devel] help on bootstaping gnumed cvs

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] help on bootstaping gnumed cvs
Date: Tue, 26 Oct 2004 11:23:18 +0200
User-agent: Mutt/

> ok, i re-bootstraped the cvs in a more or less reproducible way, here is what 
> i did:
> $ cd /somepath
> $ cvs co gnumed
> # ln -s /somepath/gnumed/gnumed/client /usr/lib/python2.3/site-packages/Gnumed
> # vi /etc/pg_hba.conf   # add at the beginning 'local all all trust' and
>     # 'host all all trust'
> # /etc/init.d/posgresql reload
> $ cd /somepath/gnumed/gnumed/server/bootstrap
Everything's fine until here.

> $ cp bootstrap-monolithic_core.conf bootstrap-gm_db_system.conf
No. No need for that.

> # cd /somepath/gnumed/gnumed/server/bootstrap

> # ./

Use instead.

> at this point i still get the "The database account [test-doc] is not 
> associated with any staff member known to GnuMed." error for all identities.
Yes, because you never bootstrapped the test data (which does, among other things).

> # su postgres
> $ psql gnumed < ../sql/test-data/test_data-Leonard_McCoy.sql
which would be the manual version of bootstrapping the test
data - which already includes

> i've been not able to do much after log in, but at least i've seen the main 
> window ;-)
well, there isn't really *that* much to "do" yet

> unless i did something very wrong, the following things were very hard to 
> find 
> and definitely need a fix:
> - the --conf option appears to be broken (you need to cp the .conf file to 
> one 
> of the hardcoded ones)
no, it does work here

> - the bootstrap script should load some test data together with the test 
> accounts
it does but you need to use the right script, eg.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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