mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-25 04:59:43 +00:00
rcourtman
46d3ca214f
`npm run dev:verify` (and `dev:verify:lab`) still passed
`tests/17-recovery-layout.spec.ts` to the integration runner. That spec
was replaced by `tests/17-proxmox-backups-layout.spec.ts` in 1c38d79937,
and `scripts/tests/test-hot-dev-bg.sh` pinned the stale path.
The stale path never failed the pack. Playwright treats spec paths as
filters, so `test --list` with main's arguments reports 10 tests in 2
files and exits 0. The backups layout guard had silently dropped out of
the managed proof pack.
Changes:
- `scripts/hot-dev-bg.sh`: the default verify command names
`17-proxmox-backups-layout.spec.ts`.
- `tests/integration/tests/17-proxmox-backups-layout.spec.ts`: the
guards need the mock-mode estate. Under the managed hot-dev runtime
(`PULSE_E2E_USE_HOT_DEV`) they skip with an `npm run mock:on` hint when
mock mode is off. They do not switch modes in place, because
`Monitor.SetMockMode` clears the runtime's active alerts and in-memory
history. Other harnesses are unchanged; Core E2E runs mock mode.
- `scripts/tests/test-hot-dev-bg.sh`: pins the new spec and checks that
every spec the default verify command names exists under
`tests/integration`. Against main's `hot-dev-bg.sh` that check fails on
the retired path. The README pin is updated the same way.
- `tests/integration/README.md`, `deployment-installability.md`:
describe the real spec and what it checks.
- Removes two unused `RECOVERY_PRODUCT_SURFACE_EXACT_FILES` lists that
named deleted files.
Verification (private stacks on pulse-dev, not the shared dev stack):
- Fixed proof-pack arguments through `scripts/run-playwright.mjs`
against a mock backend: 7 passed, 5 skipped (spec 16 needs the managed
runtime), twice. An earlier run at load ~110 timed out on clicks in
specs 17 and 18; those passed on rerun.
- Gated spec 17 with `PULSE_E2E_USE_HOT_DEV=1`: 2 skipped against a
real-mode backend, 2 passed against a mock backend. Main's ungated spec
17 fails both tests against the same real-mode backend.
- `scripts/tests/test-hot-dev-bg.sh`: 288 passed. The touched functions
fail 4 assertions with main's `hot-dev-bg.sh` and README.
- `canonical_completion_guard_test` and `subsystem_lookup_test`: 304
tests OK.
The mock backend used a reduced estate (`PULSE_MOCK_NODES=5` and
similar). The default 50-node estate did not finish starting within 25
minutes on pulse-dev at load ~100.
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.