Files
pulse/docs
rcourtman a1891e5f0c Keep open row drawers spanning the table when columns change
An open inline row drawer measured its colspan from the summary row's
visible cells only on mount and on resize. Hiding or showing a column
from View > Columns, or a column that depends on the data such as the
vCenter column, left the drawer with its old span. On the Machines
table, hiding Uptime with a drawer open shrank the header and rows to
939px of a 1375px table beside a blank phantom column, and showing
System left the drawer 79px short of the actions column.

InlineDetailTableRow now re-measures when the summary row's own cells
are added, removed or hidden, and when the requested colspan changes.
Changes inside a cell's content are ignored, so live metric updates do
not re-measure. When the span grows, Chromium keeps a fixed-layout
table's old column widths for the widened cell, so the row changes the
cell's width for one forced layout and then restores it.

The primitive's own test file becomes a registered frontend-primitives
proof.
2026-10-06 14:00:59 +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.