pub struct KaslServerConfig {
pub url: String,
pub ca_certificate: Option<String>,
pub pulse: bool,
}Expand description
Connection to a kasl-server instance: where to reach it, and how to trust it.
The agent token is deliberately absent - it lives in the OS keyring, like every other kasl credential, so a readable config file never carries one.
Fields§
§url: StringBase URL of the server, e.g. https://kasl.example.com. Stored
without a trailing slash so endpoint paths can be appended as-is.
ca_certificate: Option<String>PEM file holding the certificate authority that signed the server’s certificate.
Self-hosted deployments are routinely behind a company CA or a self-signed certificate, which the system trust store does not know. Naming the certificate here keeps verification on: the alternative - switching it off - would also accept anyone else’s certificate.
pulse: boolWhether the watcher tells this server, once a minute, if you are working, on a break, or not in a day.
Off until the employee turns it on with kasl server pulse enable:
connecting agrees to send finished days, and a live signal of whether
someone is at their keyboard is a different thing to agree to. It
lives here, beside the address, so the consent belongs to this
connection - disconnecting forgets it, and connecting to another
server does not inherit it.