v0.1.32 — native TLS + activity dates + light contrast

What's new

Native TLS — the dashboard now serves HTTPS itself

No reverse proxy required. Give pulsemon a certificate and it serves the dashboard over TLS directly:

• Install-time: set PULSEMON_CERT and PULSEMON_KEY (paths to your cert and key). When a pair is in place, the dashboard is HTTPS-only on the TLS port (443 by default) — the plain-HTTP port is not bound, so nothing is ever reachable in plaintext.
• From the dashboard: Settings → TLS / HTTPS now has a certificate panel. Pick your cert.pem + key.pem (or paste the text), choose the HTTPS port, and hit Apply. The pair is validated in memory first (cert parses, key parses, keys match) before anything is written — a mismatched pair is rejected and the running server is left untouched. Applying (or removing) the certificate restarts pulsemon automatically and the dashboard reconnects on the new scheme. Certs uploaded this way live in the data volume and survive rebuilds.
• A configured-but-missing cert file logs a loud warning and keeps serving HTTP (no crash-loop); a corrupt or encrypted key fails fast at startup with a clear message.
• pulsemon restart — new subcommand to re-apply a listener config manually (used by the dashboard flow under the hood).

Activity feed shows dates

Entries from an earlier day now render Tue, Oct 06 · 23:27:25; same-day entries stay time-only.

Light theme contrast

The metric-column dividers (PING | JITTER | LOSS) were near-invisible in light mode. The light-theme surface tiers are darker now, so dividers match the dark-theme gap.

Copy: pulse, not probe

User-facing wording now says "pulse"/"pulsing" to match the name (e.g. "pulsing is broken", "N pulse send errors since start").

Fixes

• The HTTP listener could default to port 80 when the listen address wasn't applied to the server object — now it always binds the configured address.

Upcoming

• Authentication for the dashboard
• Windows build