mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
bd4f6e36c4
Stacked on #2649, which carries its commitdcd409f9da. Once #2649 merges, this PR's diff is the single commitbf29201b19. PR 2612 deleted the never-mounted UnifiedResourceTable, andabb6f86aebretired the shared workloads-link helper. The unified-resources and performance-and-scalability contracts still described both as live owners. Each clause is checked against current source and now names the live owner, becomes a conditional rule, or goes: - System identity: the Docker hosts System column (`getDockerHostSystemBadge`, which drops runtime-only labels) and the resource drawer header. - Drawer resource labels: `createPlatformResourceLabelResolver`. These are operator-local names, not governed labels, and a table without a resolver shows raw IDs. - Same-route drawer reveal: `useWorkloadSelectionState`. Platform tables keep drawer state local. - Kubernetes cluster helpers: `agentResources.ts`, shared by `useWorkloads` and the drawer. - Workload platform scoping: `buildWorkloadsRouteSearch`. - Row policy chips and the workload-to-infrastructure href builder: now conditional or recorded as retired. No platform table renders policy chips. Code: with `infrastructureSelectors.ts` gone, `getInfrastructureSystemIdentitySortLabel` has no production caller, and `getInfrastructureSystemTitleBadges` has had none since PR 2612. Both are removed, along with the private helpers only the title helper used. Their tests either drop duplicate assertions or now assert the identity badges directly. Verification: badge suites plus `src/utils`, Docker, Infrastructure and platformPage vitest pass; the only failure is `agentInstallCommand`, which fails on macOS regardless. `tsc --noEmit` is clean, the bundle-size check passes with the same chunk set, and `contract_audit.py --check` reports no errors. A browser pass ran on an embedded production build (receipt `6c79cba8f0c6e7b0.json`) covering the Docker hosts System column render and sort plus the Docker and Machines drawers at 1440px and 390px.
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.