OS4X Core main configuration file - Revision history

Admin: /* SERVERID */

2024-09-09T16:34:52Z

SERVERID

2024-09-09T16:34:28Z

SERVERID

2023-03-31T19:23:45Z

CLIENTD_AUTH_HOST

2023-03-31T19:23:20Z

CLIENTD_AUTH_HOST

2023-03-31T19:21:43Z

CLIENTD_OVERRIDDEN_HOST

2021-09-27T12:28:40Z

DB_TLS_VERSION

2021-08-11T14:20:34Z

MySQL TLS connection parameters

2021-08-11T14:19:33Z

MySQL TLS connection parameters

2021-08-11T14:18:40Z

Variables

2021-08-10T14:56:32Z

Variables

@@ Line 80: / Line 80: @@
 ''Optional.''
-ID of the OS4X server in a cluster environment. Every OS4X server should have its own server ID, given by you.
+Numeric (integer value) ID of the OS4X server in a cluster environment. Every OS4X server should have its own server ID, given by you.
+*Min. value: -128
-Min. value: -128
+*Max. value: 127
 ==== DBTYPE ====

← Older revision		Revision as of 16:34, 9 September 2024
Line 81:		Line 81:

	ID of the OS4X server in a cluster environment. Every OS4X server should have its own server ID, given by you.		ID of the OS4X server in a cluster environment. Every OS4X server should have its own server ID, given by you.
		+
		+	Min. value: -128
		+	Max. value: 127

	==== DBTYPE ====		==== DBTYPE ====

@@ Line 104: / Line 104: @@
 ==== CLIENTD_AUTH_HOST ====
-This is an optional configuration value defining the host where an instance of the OS4X client daemon "<code>os4xclientd</code>" is running and accepting user authentication requests (and only these authentication requests, nothing more!).
+This is an optional configuration value defining the host (resolvable hostname or IP address) where an instance of the OS4X client daemon "<code>os4xclientd</code>" is running and accepting user authentication requests (and only these authentication requests, nothing more!).
 This configuration value overrides the option "<code>CLIENTD_OVERRIDDEN_HOST</code>", if configured.

@@ Line 105: / Line 105: @@
 ==== CLIENTD_AUTH_HOST ====
 This is an optional configuration value defining the host where an instance of the OS4X client daemon "<code>os4xclientd</code>" is running and accepting user authentication requests (and only these authentication requests, nothing more!).
 ==== WEBACCESS_UPLOAD_DIRECTORY ====

@@ Line 102: / Line 102: @@
 ==== CLIENTD_OVERRIDDEN_HOST ====
 If you want OS4X Webaccess to connect to an alternative OS4X client daemon (possibly on a remote server), set here the resolvable hostname or IP address of the server. All OS4X client daemon communication (i.e. authentification, job generation) will take place on this server.
 ==== WEBACCESS_UPLOAD_DIRECTORY ====

@@ Line 117: / Line 117: @@
 *TLSv1.1
 *TLSv1.2
 or a mix of it, like:
 *TLSv1.2,TLSv1.1,TLSv1

@@ Line 110: / Line 110: @@
 ==== MySQL TLS connection parameters ====
 Since OS4X release 2021-08-10, encrypted database connections are supported. MySQL started with version 5.7 to support encrypted connections via TLS. Please follow their online documentation about valid configuration values for i.e. protocols and cipher support: https://dev.mysql.com/doc/refman/en/encrypted-connection-protocols-ciphers.html
 ===== DB_TLS_VERSION =====

← Older revision		Revision as of 14:56, 10 August 2021
Line 107:		Line 107:

	This feature is mainly used when installing OS4X Webaccess on a remote server (i.e. remote co-location). The same directory name must exist on the host running the OS4X client daemon for job generation. In most common cases, this is done by mounting the same directory with the exact name from the remote server on the host running the OS4X client daemon.		This feature is mainly used when installing OS4X Webaccess on a remote server (i.e. remote co-location). The same directory name must exist on the host running the OS4X client daemon for job generation. In most common cases, this is done by mounting the same directory with the exact name from the remote server on the host running the OS4X client daemon.
		+
		+	==== DB_TLS_VERSION ====
		+	Since OS4X release 2021-08-10, the variable DB_TLS_VERSION defines an optional description of the used communication encryption standard, which is provided in the MySQL/MariaDB handshake. The following values are possible:
		+	*TLSv1
		+	*TLSv1.1
		+	*TLSv1.2
		+	or a mix of it, like:
		+	*TLSv1.2,TLSv1.1,TLSv1

	== Examples ==		== Examples ==