[Gnumed-devel] (Another) Install of GnuMed (this time on Debian "Sarge")

[Michael Bonert]

Hi Everyone,

I installed GnuMed on Debian "Sarge".  Notes are below.  
Problematic is that I cannot call up any of the patients
(and am thus locked out of many of the pages).  Help on
this would be appreciated.

Installation aside, it would be wonderful if the manuals 
went Wiki.  It seems I'm the install guy-- and every once 
in a while I post a set of instructions of how I managed 
to get (most of) GnuMed doing what it can do.  I'd much 
rather edit the manual-- than make a post to this list.  
The posts seem to be short-lived... and the manuals 
horribly out-of-date.

Cheers,
Michael

--------------------------------------------------
GnuMed Install Notes 

Operating System: Debian GNU/Linux 'Sarge' / KDE 3.2.2 
Hardware: Toshiba Satellite A-20
Date: June 15, 2004.
--------------------------------------------------

Older Debian install notes are here:
http://lists.gnu.org/archive/html/gnumed-devel/2004-01/msg00047.html
http://lists.gnu.org/archive/html/gnumed-devel/2004-01/msg00011.html
(These notes borrow a bit from the above)

Debian 'Sarge' install notes:
http://individual.utoronto.ca/bonert/debian_install.html
-----


#apt-get install cvs

SET-UP OF SSH KEY
$cd ~/.ssh
$echo "Protocol 2" > ~/.ssh/config
$ssh-keygen -t dsa
        <return> to accept ~/.ssh/id_dsa

---
$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/home/michael/.ssh/id_dsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/michael/.ssh/id_dsa.
Your public key has been saved in /home/michael/.ssh/id_dsa.pub.
The key fingerprint is:
<SNIP>
paste contents of:
         ~/.ssh/id_dsa.pub
into area on:
        https://savannah.gnu.org/account/editsshkeys.php


$ cd
$ mkdir gnumed

# apt-get install cvs


$ cvs -z3 -d michaelb @ subversions.gnu.org:/cvsroot/gnumed checkout gnumed
    ALTERNATE:
    $ cvs -z3 -d:ext:anoncvs @ subversions.gnu.org:/cvsroot/gnumed checkout 
gnumed
        no spaces before and after '@'
        
# apt-get install postgresql
Success. The database server should be started automatically.
If not, you can start the database server using:
    /etc/init.d/postgresql start


# apt-get install python-pgsql
# apt-get install libwxgtk2.4-python
# apt-get install pgaccess      # not required but nice to have


TESTING WXPTYHON
$cd /home/michael/gnumed/gnumed/client/wxpython
$python gmAbout.py
        (woohoo -- saw the text scroll)
        
CHANGING POSTGRES PASSWORD
$ su
# passwd postgres
        (enter new passwd)

$vi postgresql.conf
        changed "#port = 5432" to "port = 5432"
        

MODIFICATIONS TO "/etc/postgresql/pg_hba.conf"
--------------
#
# TYPE  DATABASE    USER        IP-ADDRESS        IP-MASK           METHOD
#
#host    all         all         127.0.0.1         255.255.255.255   trust

local   template1   postgres                                        ident 
sameuser
local   template1   all                                             md5
local   gnumed      all                                             md5
host    gnumed      all         127.0.0.1         255.255.255.255   md5

--------------
ALL OTHER LINES ARE COMMENTED-OUT


$ su
# kill [pid for postmaster]
# su postgres
$ /usr/lib/postgresql/bin/postmaster -D /var/lib/postgres/data/ &       
        # restarts postmaster    --- not elegant... but it works
        
testing database
        $ createdb test
        CREATE DATABASE
        $ dropdb test
        DROP DATABASE

ENSURE THE STUFF DOESN'T EXIST
$ su
# su postgres
address@hidden $ dropdb gnumed
address@hidden $ dropuser gm-dbowner

BOOTSTRAPING -- THE ROUND ABOUT WAY
$ su
# chown -R postgres:postgres /home/michael/gnumed
# su postgres
$ cd /home/michael/gnumed/gnumed/server/bootstrap
$ source redo-public.sh
        - answer yes to all
        - set password to what your heart desire--but 
          remember it for future use
$ exit 
# chown -R ?michael:michael /home/michael/gnumed
# exit

$ export PYTHONPATH=/home/michael/gnumed/gnumed

RUNNING GNUMED
$ cd /home/michael/gnumed/gnumed/client
$ source gm-from-cvs.sh

LOGIN AS 'any-doc' password is 'any-doc'


COMMENTS -
The bootstrapping procedure is messy at the moment.  Reason: one has to be
user 'postgres' ... it is 'cause of Debian I've been told--Debian forces
the use of "IDENT" in the 'pg_hba.conf'.  

THE UGLY HACK - If the ownership of the files isn't changed from 'michael'
to 'postgres' the bootstrapping craps-out because it doesn't have the
required permissions.

WHAT TO DO?
My proposed solution is more clearly dividing the components that belong to  
(1) the server, and 
(2) the client  
Dividing up the components more clearly will make packaging easier
(Andreas will be happy).  Also, it will allow us to write a little script
that copies all the files required by the server for bootstraping to a
postgres (user) subdirectory. (Required files are sql files, bootstrapping
files and what they these files depend on (a few modules)).  Copying the
files into a postgres subdirectory will avoid that the bootstrapping
craps-out and make the install relatively seemless for the people
working from the CVS version.