- Feb 13, 2024
-
-
- Feb 17, 2023
-
-
Martin Christoph Hierholzer authored
-
- Jan 13, 2023
-
-
Jens Georg authored
-
- Feb 19, 2021
-
-
Martin Christoph Hierholzer authored
Why: Techlab wants to be independent of hostnames which are defined by their customers. Also mutliple installations with identical configuration (e.g. for test setups) can now be done by customers without support by Techlab. How: A config_label can be defined in /etc/ConfigGenerator/config_labels for each server type. If this file is found and the server type is defined in the file, the specified config_label is used instead of the hostname, to identify which instance to install. Squashed commit of the following: commit 45a63a6a Author: Patrick Nonn <nicodemous@gmxpro.net> Date: Fri Feb 19 10:40:55 2021 +0100 Changed behaviour of backup script. Instead of differing between local and remote backup by itself, a flag "--force_local" has to be set as the first argument, when calling/starting the script. If the first argument is not that flag, the usual arguments are expected. Added explanation for config file to README.md. commit fa8e39d1 Author: Patrick Nonn <nicodemous@gmxpro.net> Date: Thu Feb 18 13:46:54 2021 +0100 Changed configuration file from /etc/llrfctrl.conf to /etc/ConfigGenerator/config_labels. Added "config_file" to easier change that file path in the future. commit 5369a43f Author: Patrick Nonn <nicodemous@gmxpro.net> Date: Thu Feb 18 10:48:17 2021 +0100 Added ability to define configuration from /etc/llrfctrl.conf instead of hostname. For other uses (i.e. LDAP) the real hostname is used. The file /etc/llrfctrl.conf should contain <server_type> <config_label> pairs. <config_label> has to be represented in the host-column in hostlist. If the file /etc/llrfctrl.conf is not present, the hostname will be used.
-
- Feb 09, 2021
-
-
Geogin Varghese authored
-
- Jan 07, 2021
-
-
Geogin Varghese authored
-
- Dec 26, 2020
-
-
Geogin Varghese authored
This provides examples for basic use cases.
-