GNUmed configuration files
GNUmed uses the standard INI style configuration file format. The extension
.conf is used for all config files.
Lists (options spanning several lines) are defined slightly differently from some other INI file parsers. They work very similar to PostgreSQL dollar quoting in stored procedures. Assume we want to define a list
users in a group
preferences. This would be the relevant section in the config file:
[preferences]
users = $users$
McCoy
Spock
Kirk
$users$
Default configuration files
GNUmed uses a few built-in configuration file names. All of them can be overriden by the command line option
--conf-file=FILE
where
FILE
is the name of the configuration file you want to use instead. Make sure this file is writable by the user as it will be used to store default settings.
GNUmed will try to work around missing configuration files by providing sensible defaults without exhibiting surprising behaviour.
/etc/gnumed/gnumed-client.conf
This file can be used to define system-wide backend profiles. Those profiles will be available through the login dialog in addition to those defined elsewhere. The file will be opened read-only.
On non-Unix systems this file will be stored in other directories. Please refer to the
wxPython documentation to find out where.
~/.gnumed/gnumed.conf
Additional backend profiles can be stored in this file. They will be added to the list of profiles available from
/etc/gnumed/gnumed-client.conf
. This file is also used to store user preferences which need to be available before a connection to the database has been made. Therefore the user needs write access to it.
Configuration information about the
workplace,
slave mode and
external patient sources is also found here.
./gnumed.conf
If no
~/.gnumed/gnumed.conf
file is found GNUmed will scan the current directory (from which it was invoked) for a file
gnumed.conf
. This allows starting GNUmed from an arbitrary directory (such as a copy of the CVS tree) without needing a
gnumed.conf
installed in
~/.gnumed/
.
mime_type2file_extension.conf
This file is used by GNUmed to assist in finding a suitable filename extension for certain mime types such as when displaying archived documents. It is only needed if the Operating System cannot figure out by itself how to display files of a certain type without the filename having an extension. This has mainly been observed on MS/Windows, particularly with bitmap type files.
GNUmed searches for this file in the system-wide (that is
/etc/gnumed/
on UNIX) and user-level (say, on UNIX,
~/.gnumed/
) configuration directories. If you cannot figure out what your Operating System thinks those directories should be check the GNUmed log file. It tells you where GNUmed looks for the file on your machine.
The file must contain a group
[extensions] under which there can be one option per mime type specifying the extension to use on files of said type. Set the value to the raw extension only, omitting the ".", like so:
[extensions]
# set extension for bitmap files (mime type <image/x-bmp>) to "bmp" (IOW, they should read "<filename>.bmp")
image/x-bmp = bmp
|
Das Urheberrecht © liegt bei den mitwirkenden Autoren. Alle Inhalte dieser Kollaborations-Plattform sind Eigentum der Autoren. Ideen, Anfragen oder Probleme bezüglich TWiki? Feedback senden
|