Server Config File

{
	"http": {
		"port": 3000,
		"session_secret": "ssshhhhh",
		"username": "admin",
		"password": "admin",
		"tls": {
			"port": 3443,
			"key": "config/83473599-localhost_3000.key",
			"cert": "config/83473599-localhost_3000.cert"
		}
	},

	"tcp": {
		"port": 5000,
		"asking_timeout": 10
	},

	"udp":{
		"port" : 7000
	},

	"sqlite": {
		"name": "config/chain.sqlite3",
		"max_connections" : 3000, // number of entries
		"trim_timeout" : 300 // in sec
	}
}

If you change any of these ports, then you will need to also change them for the kiosk configuration files. You will also need to restart the server'

See: Config File Configuration (ACQ Plugin)

See: Config File Configuration (Standalone)

Config File Sections as follows:

http

Field	Description
port	TCP port the server listens on for the configuration portal (not secure) - shoudl be hidden behind a firewall
session_secret	Used to sign the browser session ID cookie when logging into the portal.
username	Username used to log into the web portal
password	Password used to log into the web portal
tls	HTTPS version of the web portal. The port it loistens on, and the security certificate to use. Should still be firewalled off

tcp

Name	Tags
port	The TCP port to listen for kiosk and operator connections from
asking_timeout	How long (in seconds) a kiosk or operator can take to login

udp

Name	Tags
port	The UDP port to use, this is used to initially establish the connection between the kiosk and operator (a bit like the STUN server approach)

sqlite

Name	Tags
name	Filename of the SQLite Database
max_connections	Maximum number of connections, shouldnt need to change this
trim_timeout	How often the database cleans its self up and removes old logs etc (seconds)

Server Config File

The config file for the server is located in config/default.json and looks like the following.

Config File Sections as follows:

http

udp

sqlite