GNUmed - salaam.homeunix.com
Hi all,
Due to the unexpected loss of the (dyndns) domain salaam.homeunix.com the
public database cannot be reached under this domain any more.
The new domain is publicdb.gnumed.de. This needs to be fixed in the config
files and will be in gnumed-client 0.8.7 and 0.9.0.
Until those versions are release (not yet determined) one can use the attached
(fixed) config file as a replacement or fix it manually in the config file.
Place it in /etc/gnumed/
Best regards,
Sebastian Hilbert
# -------------------------------------------------------------
# GNUmed client config file
# -------------------------------------------------------------
# This file can be used as:
#
# ~/.gnumed/gnumed.conf
# /etc/gnumed/gnumed-client.conf
#
# See also:
#
# http://wiki.gnumed.de/bin/view/Gnumed/ConfigFiles
# http://wiki.gnumed.de/bin/view/Gnumed/CustomizingClientStartup
# http://wiki.gnumed.de/bin/view/Gnumed/ConfigurationStoredInBackend
# http://wiki.gnumed.de/bin/view/Gnumed/WorkPlace
#
# man gnumed
#
# -------------------------------------------------------------
[preferences]
profile = GNUmed database at salaam.homeunix.com (gnumed_v14@salaam.homeunix.com)
login = any-doc
[backend]
# "any-doc" is the standard account installed with
# any stock installation, it should be disabled when
# going into production because the password is known
# to all (it is "any-doc" as well)
#
logins = $logins$
any-doc
$logins$
profiles = $profiles$
GNUmed database on this machine (Linux/Mac)
GNUmed database on this machine (Windows)
GNUmed database at publicdb.gnumed.de
$profiles$
# If the system locale matches this value a mismatch
# with the database locale will be ignored.
# Remove this option if you want to stop ignoring mismatches.
#
#ignored mismatching system locale = de_DE@euro
# If GNUmed cannot detect the proper timezone from system
# information or you want to use a timezone different from
# the system GNUmed is running on you can explicitly set
# the time zone here.
# Note that the timezone must be a valid PostgreSQL timezone
# string. If in doubt consult the PostgreSQL docs.
# If you don't want to change the timezone GNUmed detects
# in the system you need to comment out this option.
#
#client timezone = Europe/Berlin
[profile GNUmed database on this machine (Linux/Mac)]
host =
port = 5432
database = gnumed_v14
public/open access = 0
help desk = Your own IT support <needs configuration>
[profile GNUmed database on this machine (Windows)]
host = 127.0.0.1
port = 5432
database = gnumed_v14
public/open access = 0
help desk = Your own IT support <needs configuration>
[profile GNUmed database at publicdb.gnumed.de]
host = publicdb.gnumed.de
port = 5432
database = gnumed_v14
public/open access = 1
help desk = GNUmed Development List <gnumed-bugs@gnu.org>
[workplace]
# here you can define profiles for XDT files
# provided by other applications such as
# German practice management software
#
XDT profiles = $XDT profiles$
$XDT profiles$
# default is 9999 if not set
#
#xml-rpc port = 9999
# default is gnumed-client if not set
#
#slave personality = <personality>
# Set the help desk contact information for your
# GNUmed installation here. If this includes a
# valid email address that address can be used
# to email error logs to on request.
help desk = GNUmed Development List <gnumed-bugs@gnu.org>
# Which workplace to use.
#
# http://wiki.gnumed.de/bin/view/Gnumed/WorkPlace
#
# This will influence which plugins are loaded and
# which configuration values are used. The default
# workplace hardcoded into GNUmed is called:
#
# name = Local Default
#
# Another useful workplace for testing would be "Clinician".
#
# If there is a problem with a workplace such that
# GNUmed cannot successfully load plugins you can
# set the name to
#
#name = System fallback
#
# which will make GNUmed start with a minimal set of
# plugins. After fixing the problem reset the name
# to whatever you previously used, or re-comment it
# out.
#
name = GNUmed Default
#name = System fallback
#name = Clinician
#name = <a workplace name>
[XDT profile generic XDT connector]
# a short (!) description of the xDT source,
# this will be shown to the user when activating
# a patient from an xDT file
source = xDT allgemein
# this is the name of the file eventually containing
# the patient data in xDT format
filename = patient.xdt
#DOB format =
#encoding =
[XDT profile Terminiko]
filename = /home/ncq/gnumed/tmp/terminiko2gnumed.xdt
[XDT profile TurboMed/Win]
source = TM/Win
encoding = cp437
DOB format = %d%m%Y
filename = C:\Turbomed\patient.xdt
[AU PracSoft PATIENTS.IN]
source = PracSoft (fake)
filename = ~/gnumed/xDT/PATIENTS.IN
[CA Medical Manager MSVA]
# typically something along the lines:
#filename = <DRIVE>:\somewhere\VMEDICAL\EXPORT\PATEXPORT
# in the git tree:
filename = ../data/other/CA-MSVA.txt.test
Reply to: