Complete guide to install and configure the Liderit Daemon on your workstation
Your system administrator must register your workstation in the Liderit Panel first. Once registered, you'll receive:
office-pc-01)client.crt, client.key, ca.crt provided by adminThe Printer Daemon uses secure SSL/TLS certificates for encryption. Certificates are issued and delivered by an administrator. Client installers do not issue or download certificates.
cert_dir and each filename separately, then write those values into [tls] in your config.tomlcert_dir = "./certs", cert_file = "client.crt", key_file = "client.key", ca_file = "ca.crt"server.address = "api.liderit.ro:14545"server.client_key (required value)server.reconnect_interval = "5s"storage.transfer_dir = "./transfers"storage.temp_dir = "./tmp"cleanup.after_print = truecleanup.after_transfer = false — if true, the saved file is deleted after a successful non-print transfer (including after any rule move)config.toml or (Windows) via the tray config editor — see File transfers & storage rules below.liderit-connector-setup.exe (or download it from the Panel when a connector release is published).liderit-connector-setup.exe → Run as administrator and follow the wizard (certificates, server address, client key, printers, paths).%LOCALAPPDATA%\LideritConnector\config.toml (unless the service was installed with a custom -config path).install-windows.ps1 may still exist in some source bundles for automation only; normal end-user install is the .exe above.
chmod +x install-linux.sh
Run installer:
sudo ./install-linux.sh
client.crt, client.key, and ca.crtsystemctl status liderit-connectorOnce the Printer Daemon is installed and running, it automatically connects to the Liderit server using the credentials provided during installation.
You can verify your connection is working by checking:
Windows:
Linux:
systemctl status liderit-connector
journalctl -u liderit-connector -f
Once your Printer Daemon is online, your administrator can send files to your workstation for printing through the Liderit API.
During installation, you selected which printers to register. Your administrator can:
When the API sends a job as a file transfer (not a print job), the daemon writes the file to [storage].transfer_dir (or to temp_dir if transfer_dir is empty). Directories are created if they do not exist.
You can define one or more storage rules so that, after the file lands in transfer_dir, it is moved into another folder when its base filename matches. This only applies to non-print transfers.
ruleId with different ruleMatch / ruleLocation values (for example several different filename prefixes).ruleLocation is created automatically if missing.ruleLocation paths are resolved from the directory that contains your config.toml, same as transfer_dir and temp_dir.ruleId = 4) is invalid, that rule is skipped (check daemon logs); the file stays in transfer_dir unless another rule matches.ruleId)ruleId |
Match type | ruleMatch means |
|---|---|---|
| 1 | Starts with | Filename begins with this literal string (case-sensitive). |
| 2 | Ends with | Filename ends with this literal string (case-sensitive). |
| 3 | Contains | Filename contains this substring (case-sensitive). |
| 4 | Regex | Entire filename must match this Go regular expression. |
| 5 | Extension | File extension equals ruleMatch; you may include or omit the leading dot; comparison is case-insensitive (e.g. ruleMatch of .pdf or pdf matches report.PDF). |
config.tomlDefine each rule as [[storage.rules]] with the same three fields. Canonical keys:
[storage]
transfer_dir = "./transfers"
temp_dir = "./tmp"
[[storage.rules]]
ruleId = 1
ruleMatch = "INV_"
ruleLocation = "./transfers/invoices"
[[storage.rules]]
ruleId = 5
ruleMatch = ".pdf"
ruleLocation = "./transfers/pdf"
For compatibility, the same three fields may use legacy snake_case names (one block shown here; every [[storage.rules]] entry can use either style):
[[storage.rules]]
rule_id = 1
rule_match = "INV_"
rule_location = "./transfers/invoices"
Open the connector system tray menu → Edit Config… → Storage tab. Set transfer_dir, temp_dir, and use Add / Edit / Remove for rules (same ruleId types as in the table). Click Save & Reload so the service reloads the config.
Edit config.toml with a text editor, then restart the service (e.g. sudo systemctl restart liderit-connector) or use your deployment’s reload procedure so the daemon reloads configuration.
cleanup.after_transfer: When set to true, the daemon deletes the file after a successful non-print transfer. Deletion applies to the file’s final path (after any rule move). Keep this false if you need to keep delivered files on disk.
Start/Stop from Services:
From PowerShell (Admin):
Start-Service LideritConnector
Stop-Service LideritConnector
Restart-Service LideritConnector
Get-Service LideritConnector
sudo systemctl start liderit-connector
sudo systemctl stop liderit-connector
sudo systemctl restart liderit-connector
sudo systemctl status liderit-connector
View logs:
sudo journalctl -u liderit-connector -f
Windows:
%LOCALAPPDATA%\LideritConnector\connector.exe -uninstall
Linux:
sudo ./uninstall-linux.sh