Parameters defaulting from environment

The following environment variables are used by software library:

Note: Those variables can be passed as parameters with impact_InitProcess2

Webserver authentification setup :

SETUP_USER see impact_InitProcess
SETUP_SECRET see impact_InitProcess
ADMIN_USER see impact_InitProcess
ADMIN_SECRET see impact_InitProcess

Webserver secure :

SSL_CERTIFICATE_PATH : path to the SSL public certificate
SSL_PRIVATE_PATH : path to the SSL private certificate

Network access :

LICENSE_SERVER : the SOUND4 license server's URL
LICENSE_SERVER_PROXY : proxy server to use for licenses [user:pass@]host:port
LICENSE_CERT_DIR : optional certificates dirs for HTTPS verification
LICENSE_CERT_CHECK : if "false", do not check HTTPS certificates

Parameters

The following parameters can be set before creating instance, but are never taken from environment.

Run mode:

FILE_MODE=seconds : force file mode, settings the maximum estimated audio duration (non realtime, wait license ok to process)
STATE_FILENAME=filename : force this instance to store its state in file named filename.json (instead of state.json)
STATE_ONAIR=filename : force this instance to store its on air preset name in file named filename.onair (instead of none). Used for sharing between instances.
STORAGE_RO=notempty : force the storage in read-only mode
STATE_RO=notempty : force the state in read-only mode (but can save presets/auth)
WAIT_LICENSE=notempty : force to wait the license load before starting (always in file mode)

Preset sharing

You can use the same folder for multiple instances so they share their presets.

In this case, you should use a different STATE_FILENAME per instance so they keep their settings and on air presets separated. If not, each time settings or onair preset are changed, the changes will be reflected to the other intances using same STATE_FILENAME.

You may use the same STATE_ONAIR for multiple instances sharing the folder, so that changing the on air preset on one immediatly changes the on air preset on other instances using the same STATE_ONAIR. If the instance has pending unsaved changes in the on air preset, it will not be updated automatically to avoid loosing changes.