mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-23 11:46:28 +00:00
rcourtman
80d4558b42
The Recovery and Snapshot Age threshold sections rendered two Global Defaults surfaces at once, the live editor row plus a synthetic read-only resource row of the same values. Both looked editable but the synthetic row's pencil editor saved through findThresholdResource, which never finds the pseudo-resource, so its edits were dropped silently. Reported in #1680 by FabienD74. The synthetic rows are gone; the always-live editor row is the single surface in both table and card layouts. The dead editScope field and its unreachable saveEdit branches go with them. The size columns move from Recovery to Snapshot Age where they belong. BackupAlertConfig has no size fields, so on Recovery they always rendered an inert Off. SnapshotAlertConfig sizes are live in the alert engine (backup_snapshot.go) but were previously invisible and, worse, unpersistable. The records now carry the normalized warningSizeGiB and criticalSizeGiB metric keys the column editor reads and writes, and applyAlertsConfigToSnapshot plus buildAlertsConfigurationPayload carry the size fields through load and save instead of stripping them. Verified end to end against the mock dev stack, PUT then GET returns the saved sizes and a reload shows them. Guests in the VMs & Containers section now sort by display name with vmid as tiebreaker. The old vmid-first order looked random because the rows do not render the vmid, which is what the sorting complaint in #1680 was about. Dropping the phantom columns and the per-row bulk-edit checkbox also brings the Recovery table under the desktop width budget, so it renders as a table at 1280px and up instead of falling back to cards.
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.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- 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
- 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.