Hard coded configuration will be overwritten every time you're updating Domestik's client.

To avoid that, you may create a file named /usr/local/Domestik/Client/configuration.lua and centralizing all clients configuration.

Content of this file has priority ; in other words, if you define DOMESTIK_USER here, content of dmkcheckd is ignored.

This is the configuration.lua for my Clevo i5 laptop is :

DOMESTIK_USER='PiV:######'
DOMESTIK_SERVER='actif.chez.moi:8000' 
DOMESTIK_PROTOCOL='http'
DOMESTIK_INTERVAL=300

probes_list = {
        temp1 = { "/sys/class/hwmon/hwmon0/temp1_input", "err_alarm", "normMilli" }
}

DOMESTIK_USER, DOMESTIK_SERVER, DOMESTIK_PROTOCOL and DOMESTIK_INTERVAL : overwrite Domestik's server connection informations used in dmkcheck and dmkcheckd.

Notez bien : if DOMESTIK_USER is redefined, all DOMESTIK_s have to be as well.

List of hardware probes. It share the same format as of Probes/linux_hardware.lua ... with the following differences :

• It is MANDATORY that functions name are stored as string.
• this table MUSTN'T be local (otherwise, it isn't exported outside this configuration file).

Reason behind : functions are defined inside Probes/linux_hardware.lua only and consequently, they are undefined at the moment configuration.lua is loaded.