mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 14:00:29 +00:00
rcourtman
a0770b87bb
The three-shard backend gate landed with a 16 GiB admission requirement that exceeded the 8-vCPU PVE worker's own idle availability (measured 16.1-16.7 GiB, and 14.1-14.9 GiB beside the sibling release compilers), so the next release would have hard-failed at admission before running a single test. Direct probes on the worker measured the complete gate at a ~6-7.5 GiB footprint (8.9 GiB MemAvailable floor from a 16.4 GiB start, zero swap), so admission now requires 10 GiB for three shards and 8 GiB for two, and degrades the shard count instead of failing the release when the bounded wait expires without headroom. Shard CPU is now weighted by planned test volume from the plan manifest. Top-level tests execute serially per test-binary process, so width mainly buys runtime, GC, and race-detector headroom for the 3595-test prefix shard; the ~15-test wait-bound tails cannot use it. Probes measured the prefix shard at 569s with 2 procs versus 484s with 4, with total allocation still equal to the worker's vCPU count. Validated by three direct runs of the canonical script on the worker: the full gate passed in 8m10s wall (auto-admitted three shards, procs 4/2/2, shard walls 484s/331s/224s) against the 12m09s two-shard release job measured in run 32514803052. One rig run also proved the gate fails closed: a stale contract pin failed the non-API graph and the harness terminated every descendant shard process.
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.
- 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.