mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 14:00:29 +00:00
rcourtman
daf2ad7ff9
Completes the wrapper-teardown rule across the remaining branches. The QNAP install and both uninstall paths still used a bare pkill -f "start-pulse-agent.sh" and still stopped the agent before its wrapper. The bare pattern is narrower than it looks and wider than it should be. It does NOT match a co-installed agent's supervisor, so the sibling case was already safe; what it does match is anything where the unescaped dot stands in for another character and the unbounded tail keeps going, including a .bak copy of the wrapper and an editor session holding it open. Escaping the dot and bounding the far end removes both without narrowing the intended match. Ordering is the more consequential half. A wrapper is a watchdog, so stopping the agent while its wrapper still loops only races the respawn. QNAP and the uninstall paths now stop the supervisor first, which is what the contracts already required of every branch that writes and launches a wrapper. Uninstall keeps a deliberately broader match than install, with no leading path separator, so it still reaches a wrapper invoked by a relative path or stranded at a superseded location. Both contracts now carry that distinction and the teardown ordering rule, which each had stated only for install. Guarded by two tests that pin every wrapper kill in the file rather than one branch: one requires the escaped dot and the bounded tail everywhere, the other walks each stop block and fails if an agent kill precedes its wrapper kill. Both were confirmed to fail against the pre-fix QNAP block.
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.