[Gnumed-devel] re: Sidux install

[Geordie]

Peter and Karsten

Maybe your experience can be of value to Peter who is on Sidux as well ?

For me to have Gnumed running in sidux, I have had to deviate from the information provided in the wiki. First is the pg_hba.conf mine is set up as follows

nano /etc/postgresql/8.3/main/pg_hba.conf

# Database administrative login by UNIX sockets

# allow some people to impersonate "postgres" when connecting to template1

local template1 postgres ident postgres-alikes

# replace N with the database version you want to install

local gnumed_vN postgres ident postgres-alikes

# allow real "postgres" to connect to all other databases, too

local all postgres md5

# allow some people to impersonate "gm-dbo"

local template1 gm-dbo ident gm-dbo-alikes

# allow anyone knowing the proper password to log into

# our GNUmed databases

local samegroup +gm-logins md5

# TYPE DATABASE USER CIDR-ADDRESS METHOD

# "local" is for Unix domain socket connections only

local all all md5

# IPv4 local connections:

host all all 127.0.0.1/32 md5

# IPv6 local connections:

host all all ::1/128 md5

Apparent indent user has to be configuired in the the new versions of Postgres and it was recommended to use md5 for beginners. I am all for that. This configuration is set up for a single machine and localhost

net_install-gnumed_server.sh I had a terrible time trying to get this script to work. I manually installed all the requirments for gnumed-server with apt-get. However this was before I had changed pg_hba.conf. After that was changed the script worked. I cannot confirm if the apt-get part of the net_install works. I assume it does for the rest of the script works.

/etc/gnumed/gnumed-client.conf

The Wiki suggest using this .conf file however it is not installed with 0.3.8 so I used this etc/gnumed/gnumed.conf and it looks like this

nano etc/gnumed/gnumed.conf

# GNUmed system-wide configuration file

# -------------------------------------------------------------

#

# see also: http://wiki.gnumed.de/bin/view/Gnumed/ConfigFiles

#

# -------------------------------------------------------------

[workplace]

# This name is used to describe the workstation at the

# business logic level, eg. "ultrasound room machine 1",

#

# Many configuration options stored in the backend

# are tied to this name.

name = GNUmed Default

[backend]

# during login the user can chose from several

# profiles defining which GNUmed database server

# to connect to,

#

# the profiles themselves are defined further below

#

profiles = $profiles$

public GNUmed database

local GNUmed database

$profiles$

[profile public GNUmed database]

host = salaam.homeunix.com

port = 5432

database = gnumed_v9

#encoding = UTF8

# this option controls whether the database is in-production

# storing real patient data or is a public database with

# open access for testing and development

#

# among other things it controls whether log files are by

# default attached to bug reports mailed out to developers,

# for real patient databases set this to 0

public/open access = 1

# this option defines who is in charge of tech support

# for this GNUmed database,

# public databases are serviced on the mailing list,

# set this to an internal staff address for real

# patient databases

help desk = GNUmed Development List <address@hidden>

[profile local GNUmed database]

host = localhost

port = 5432

database = gnumed_v9

#encoding = UTF8

# this option controls whether the database is in-production

# storing real patient data or is a public database with

# open access for testing and development

#

# among other things it controls whether log files are by

# default attached to bug reports mailed out to developers,

# for real patient databases set this to 0

public/open access = 0

# this option defines who is in charge of tech support

# for this GNUmed database,

# public databases are serviced on the mailing list,

# set this to an internal staff address for real

# patient databases

#

# Debian: FIXME: This needs to be configurable via debconf

# Something like Your own IT support <needs configuration>

help desk = GNUmed Development List <address@hidden>

This is a plain setup and I have not changed the default settings.

I may have changed another setting, but for the moment this seems to work.

Karsten, I was wondering what will happen when sidux gets KDE 4.2 in January?

If there is anything else I can help with, let me know.

Geordie