Files
pulse/docs
rcourtman 068893f83f Hide section tabs and lift table preview caps in kiosk
Kiosk is the read-only wall display from issue 917. With the filter bars
gone (#2779) two things still assumed someone at the keyboard: the
platform section rail, which the maintainer's replies on #917 and #1102
say kiosk hides, and the Proxmox nodes preview that stops at twelve rows
behind a Show all button.

PlatformSectionTabs now stays unmounted in kiosk and
createPlatformTablePreview shows every row with no toggle, so both rules
live in the shared primitives and every platform page and the Backups
view rail follow. The rail mounts fresh when kiosk ends so its phone
scroll controls bind to the new element, and the preview keeps its
expansion across kiosk so an open node drawer is not stranded.

On the 50-node mock estate the rail cost a 1280x400 display 53px, and
the cap kept 38 nodes off it, including the offline node ranked 23rd;
kiosk hides the navigation with its Alerts count, so the table rows are
where a node going down shows. Drawer search fields and the node-scoped
Guests heading reset stay, since a click or a chosen URL narrows the
page and these are the way back; the contract records why next to the
FilterBar kiosk rule and corrects the stale preview row counts (twelve
and six).
2026-10-10 09:55:39 +01:00
..
…
2026-10-05 21:53:41 +01:00
…
…
2026-10-05 21:53:41 +01:00
2026-10-05 21:53:41 +01:00

Pulse documentation

Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.

Start here

  • Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
  • Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
  • Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
  • Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
  • Configure Pulse — authentication, notifications, discovery, retention, and system settings.
  • Deployment models — data locations, lifecycle, and differences between supported deployment paths.
  • Troubleshooting and FAQ — common failures, diagnostics, and operator questions.

Localized getting started guides: Deutsch · Español

Platforms and agents

VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.

Monitoring and operations

Pulse Intelligence

Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.

Security, privacy, and access

Plans and managed access

Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.

Development and reference

Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.

Previous versions and migrations

Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.