mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
ae0158ba60
Rebuilds #2435 as one commit on current main. Its branch conflicted with the Tailwind 4 move (#2443) in a host-table test; the three original commits' reasons follow. Name the last backup in Proxmox coverage, not the newest snapshot: The Coverage table's Restore column showed the newest of every artifact, including guest snapshots. A VM with a snapshot from last night and a PBS backup from three weeks ago read "Restore 18h ago" in the healthy green beside a "Needs attention" posture, and the only way to see why was the row's hover text. Guest snapshots share the guest's storage; the posture engine already refuses to count them ("snapshots alone do not prove independent recovery"), so the row contradicted the server. The column is now Last backup: the newest completed PBS snapshot or PVE backup file. Snapshot-only rows show None and carry the engine's own reason on hover, the guest snapshot keeps its dedicated column, and the sort and the backup-location filter follow the same rule. The location filter also stops treating running or failed artifacts as a latest pointer, which the unfiltered model already did. Keep Proxmox backup and node tables whole on phones: On a 390px phone the Proxmox tables clipped the values users came for. The nodes table showed six "Anal…" rows for the Analytics A–F cluster: a sixth column (temperature) left the node name four characters wide with the toggle and status dot in front of it. The backup server row showed "H…" for Healthy, and the coverage and By date rows clipped "18h ago" to "18 …" and "Running" to "Runni…". Nodes now carry the same five columns as the guest table beneath them with a wider identity cell; temperature returns from 440px, where it fits. Backup ages use a suffix-free compact form ("18h") with the full timestamp on hover. The server row keeps its status word and used percentage whole and lets the backup count return at the next width, and its stale header width classes no longer fight the colgroup. The By date row keeps its source and state badges whole while the repository moves to the row's hover title. Just above the phone projection the servers' used/total pair and the coverage posture word now fit, and at desktop width "Automation Lab Standalone" no longer truncates in the nodes table. Measured with a scrollWidth-over-clientWidth sweep of every table cell at 1440px, 560px and 390px; only identity strings still clip, each with its full text on hover. Name the archive format in By date and widen phone guest names: The By date table's Details cell showed a PVE backup's full volid, "backup-vault:backup/vzdump-qemu-1002-2026_10_02-20_10_14.vma.zst", which repeats the storage, guest type, VMID, and timestamp the row already shows in their own columns and clipped in every one of its rows on a 1440px screen. The one fact it adds is the archive format, so the cell now reads "vma.zst" or "tar.zst", the volid stays on hover and in search, and a provider with no format falls back to the file name. The coverage disclosure's evidence table follows suit. The shared guest table's phone name cell carries the expansion toggle, status dot, and backup badge before the name, so the shared 30% identity anchor left a 390px phone 66px for the name and clipped "artifact-cache-310" to "artifact-ca…". It now takes the same 38% anchor the Proxmox host table uses, which gives the name 95px while the four metric chips beside it still fit. Measured with a scrollWidth-over-clientWidth sweep at 1440px, 560px and 390px: the By date table has no clipped cell at desktop width, and on phones only long identity strings still clip. Contract-Neutral: Proxmox coverage, phone and mid-width column projections, By date Details and guest-table phone identity width are presentation only; owning unified-resources and storage-recovery notes updated; no workloads hot-path or frontend-primitives change
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
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
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
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
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
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
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
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.