mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
19b963be71
The aggregate Recovery page (`frontend-modern/src/components/Recovery/`,
`features/recovery/useRecoverySurfaceState.ts`) was deleted on
2026-05-26 (66fb198cc6), but several contracts still described it as
live, and part of its plumbing survived.
**Code**
- Deletes the recovery query serializer from `routing/resourceLinks.ts`
(`RECOVERY_QUERY_PARAMS`, `parseRecoveryLinkSearch`,
`buildRecoveryRouteSearch`, `normalizeQueryBooleanFlag`). Nothing in
production called it: the Proxmox Backups tab owns its query through
`PROXMOX_BACKUPS_QUERY_PARAMS`, and the TrueNAS Protection tab keeps its
filters out of the URL.
- Deletes `utils/recoveryItemTypePresentation.ts`, whose only production
reader was that serializer, plus its tests and registry entries.
**Contracts** (frontend-primitives, storage-recovery, unified-resources,
alerts, cloud-paid)
- Passages naming the deleted shell, section owners, event-first
workspace, filter/column models, `view=inventory`/`view=events` route
state and the retired presenters now say what exists. Recovery rows
render in the Proxmox Backups and TrueNAS Protection tabs,
`useRecoveryPoints` is the only `/api/recovery/points` reader and
normalizes every response, and rules that only governed the deleted page
are gone or reduced to a reintroduction guard (storage-recovery
forbidden paths 9-11).
- `alerts.md` no longer claims `AlertResourceIncidentsPanel.tsx`
resolves chips through `buildResolvedResourceSurfaceLinks`. That helper
was deleted on 2026-05-16, and the panel imports nothing from
`resourceLinks.ts`.
- Leaves the embed paragraphs that rcourtman/Pulse#2726 rewrites
untouched. Both PRs merge cleanly together (checked with `git
merge-tree`, and the merged guardrails file passes).
**Proof**
- New assertions: no recovery-shaped export in `resourceLinks`;
`useRecoveryPoints` hands out normalized points (rendered hook with a
mocked transport) and is the only literal `/api/recovery/` reader
alongside `useProtectionPostures`; the retired hooks and helper stay
deleted; the Backups tab keeps day in the URL and range in component
state, with view tabs above the filter bar; the TrueNAS Protection table
keeps search, status and sort out of the URL; the incident panel imports
no route helper.
- Each assertion has a negative control that fails at the intended
assertion (15 in total). Targeted vitest, `tsc --noEmit`, eslint and
prettier pass on pulse-dev.
- Browser pass on a private Vite server from this tree at 1280x800 and
390x844. Covered `/proxmox/backups/date` (day selection, 1y range,
reload), `/proxmox/backups/coverage`, and `/truenas/protection` (filter,
row details, empty state). Receipt:
`frontend-modern/browser-verification/fe79952e5bb084d8.json`.
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.