The Zegami Server and CLI are both configured via a configuration file called settings.conf which is located at C:\Program Files\Zegami\Lib\site-packages\zegami\conf\settings.confon Windows and /opt/zegami/conf/settings.conf on Linux.
Settings.conf is responsible for a range of server options and is divided up into groups of configuration items so that it is simpler to read. Configuration section headings are marked by the section name in square brackets: [ and ].
General Zegami settings.
A True or False value indicating that the server should be run in debug mode.
formats: List of strings
A comma separated list of allowed image file formats.
The full path to the directory where Zegami will store all collection images.
Used by the image processing module. This is the Deep Zoom level where the atlas texture map stops and the individual pyramids begin.
The full path to the directory where Zegami will store all collection data. In most cases it is recommended that this be the same as the collections path.
The count of CPU cores to use when processing images.
Server logging settings.
Zegami provides fine grained control over the amount of logging that is produced. In most cases level 30 will provide enough information for general use. In situations where more detail is required for debugging purposes this level can be adjusted. The available levels are: 40 – Display error messages and critical messages 30 – Display warning, error and critical messages (Recommended) 20 – Display info, warning, error and critical messages (Zegami debug level) 10 – Display debug, info, warning, error and critical messages (all module debug level) * 0 – Do not display any messages
The full path to the directory where the logs will be kept
The number of days to keep rotated logs
host: IP Address
The host name of the logging server
The port number of the logging server
Authentication plugin settings.
The name of the plugin to use for Authentication. The available options are: NoAuth – No authentication LocalAuth – Uses the local MongoDb instance to store user details * LDAPAuth – Authenticates users against an LDAP server
Enables/disables anonymous access to collections – only if the currnet licence allows it
Image plugin settings. The image plugin is responsible for loading and processing images.
The name of the plugin to use for image processing. The available options are: Vips – For fast performance on Linux only. Has stability issues and may fail to process a collection. Pillow – Pythons native image handling libraries.
destination plugin settings. The destination plugin is responsible for storing all collection related files.
The name of the plugin to use for storing collection files. The default (and only option) is: FilesystemImageDestination
Web server settings
host: IP Address or host name
The IP Address or host name of the server. (Only applicable it the Flask server which is used on windows installs and web development).
The port which the web server is running on (Only applicable it the Flask server which is used on windows installs and web development).
MongoDB database connection details. By default is set to work with the locally installed instance, but this can be overridden to support a remote instance.
The IP Address or host name of the MongoDB instance (default is localhost).
The port which the MongoDB instance is running on (default is 27017).
Powered by BetterDocs