mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-23 20:25:56 +00:00
rcourtman
60527fa8ab
frontend-primitives.md still told new route-level copy to extend problemResourcePresentation, deleted inae65c5e9a2, and kept a paragraph tying that helper to ProblemResourcesTable.tsx, deleted with the dashboard overview inc743a231b8. It also kept a readability rule for that table and the dashboard Pulse Brief. Neither surface exists and no live surface implements the rule; Patrol's grouping and affected-resource counts are governed in patrol-intelligence.md. Drop the ownership paragraph and the rule, and list problem-resource among the deleted dashboard helpers that must not return. unified-resources.md still said the change and correlation summary cards default Infrastructure resource-filter links for the Patrol page and the problem-resource dashboard panels. Since the 2026-05-16 drilldown retirement the cards have no link default and render only in the resource drawer, which passes no link builder, so labels show as plain text. api-contracts.md named the dashboard Pulse Brief as a sender of autonomous_mode:false and described that field as a client override. Since4edf5f8265ChatRequest has no autonomous_mode field: the server runs every /api/ai/chat exchange in approval-required mode, as TestHandleChat_CannotElevateAutonomousModePerRequest pins, and the field that scoped handoffs still send is dropped at decode. Say so, and stop calling Patrol finding handoffs stricter than ordinary chat. The new lookup test pins the deleted helper as unowned, next to the other retired dashboard paths, so the dropped ownership claim cannot come back through the registry unnoticed.
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.