vrr/Pulse
2
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-10-03 12:47:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 14
Pulse/docs
History
rcourtman b1044cd8a4 Let replayed request ids wait for the in-flight handler instead of dropping 
Since 60d0651a88 every typed request registers a per-connection cancellable
slot that its handler goroutine releases in a deferred cleanup after sending
its result. The server replays a request id when it wants the durable receipt
again, and that replay can reach the reader before the previous handler's
deferred release runs. launchCancellableRequest treated that as a duplicate
and dropped it, so the server waited out the operation's full timeout for a
result the agent already held. The Linux x64 native-verification leg failed
this way on 12 of the last 25 main runs, always on a "replay 1" dispatch of
host update, storage cleanup, or Docker lifecycle.

Give each slot a done channel that closes on release. A replay whose id is
still registered on the same connection now waits for that release and then
runs, answering from the durable receipt. Invalid ids and over-capacity
requests are still dropped. A unit test pins the wait-then-run behaviour and
the agent-lifecycle contract records the replay rule.
2026-09-01 23:22:55 +01:00
..
api
architecture
i18n
images
monitoring
operations
release-control Let replayed request ids wait for the in-flight handler instead of dropping 2026-09-01 23:22:55 +01:00
releases Prepare v6.4.3-rc.1 release 2026-09-01 21:37:41 +01:00
security
security-review Point security disclosures at security@pulserelay.pro 2026-09-01 15:21:23 +01:00
AGENT_SECURITY.md Record rootless runtime qualification evidence 2026-09-01 22:09:22 +01:00
AGENT_SUBSTRATE.md Fail closed when installing MCP binaries 2026-08-30 05:11:55 +01:00
AI.md Fix local subscription CLI service setup 2026-08-23 09:28:44 +01:00
AI_AUTONOMY.md Rework Patrol around outcome-driven autonomous operations 2026-08-14 12:52:51 +01:00
AI_PATROL_QUALIFICATION.md Honor local Patrol preflight deadlines 2026-08-15 02:23:48 +01:00
AI_TRANSPARENCY.md Preserve secondary issue feedback 2026-08-29 12:24:03 +01:00
ALERT_ENGINE_EVOLUTION.md Mark stale spec, plan, and contract docs with verified status 2026-09-01 20:43:26 +01:00
API.md feat: add fleet health home 2026-09-01 01:02:17 +01:00
ASSISTANT_ARCHITECTURE.md
ASSISTANT_SAFETY.md
AUDIT_LOGGING.md
AUTO_UPDATE.md
AVAILABILITY_HISTORY_CONTRACT.md Mark stale spec, plan, and contract docs with verified status 2026-09-01 20:43:26 +01:00
BACKUP_TASK_TIMELINE_CONTRACT.md Define backup task timeline contract 2026-08-31 16:00:47 +01:00
CANONICAL_ALERT_ENGINE_MIGRATION_2026-03-10.md docs: mark March alert-engine migration doc superseded in scope 2026-08-26 23:37:34 +01:00
CENTRALIZED_MANAGEMENT.md
CLOUD.md
CODE_SIGNING_POLICY.md Verify exact release activation bytes 2026-09-01 13:29:06 +01:00
CONFIGURATION.md Support agent retargeting after server moves 2026-08-30 16:17:15 +01:00
DEPLOYMENT_MODELS.md
DOCKER.md Read host Docker credentials for private registry update checks 2026-08-13 10:06:26 +01:00
FAQ.md Clarify development transparency policy 2026-08-26 09:24:57 +01:00
INSTALL.md Publish portable candidate build provenance 2026-08-30 20:34:04 +01:00
ISSUE_TRIAGE.md Preserve secondary issue feedback 2026-08-29 12:24:03 +01:00
KUBERNETES.md
MAIL_GATEWAY.md
METRICS_HISTORY.md Protect shared metrics database directories 2026-08-11 15:57:17 +01:00
MIGRATION.md Document agent URL updates when the server address changes 2026-08-31 06:41:11 +01:00
MIGRATION_UNIFIED_NAV.md
MSP.md Distinguish MSP evaluation issuance from readiness 2026-08-11 14:50:47 +01:00
MULTI_TENANT.md
OIDC.md Enforce explicit SSO administrator grants 2026-08-31 00:43:42 +01:00
OIDC_SCOPE_GROUP_AUTH_FIX_SPEC.md Mark stale spec, plan, and contract docs with verified status 2026-09-01 20:43:26 +01:00
OPERATIONAL_TRUST.md
PATROL_ARCHITECTURE.md
PBS.md
PRIVACY.md Add workload history discovery lens 2026-08-30 13:49:58 +01:00
PRODUCTION_SECURITY.md Contain agent command authority 2026-08-29 22:12:41 +01:00
PROXY_AUTH.md Document the 5.x proxy-auth mitigation and its end-of-life status 2026-08-12 10:21:46 +01:00
PULSE_PRO.md Clarify Community OIDC role mapping 2026-08-26 02:31:52 +01:00
RBAC.md Enforce explicit SSO administrator grants 2026-08-31 00:43:42 +01:00
README.md docs: add focused security review packet 2026-08-16 17:13:02 +01:00
RECOVERY.md
RELAY.md
RELEASE_NOTES.md Prepare v6.4.3-rc.1 release 2026-09-01 21:37:41 +01:00
REPO_BOUNDARY.md
REVERSE_PROXY.md
SCREENSHOTS.md
SECURITY.md
SECURITY_REVIEW.md Point security disclosures at security@pulserelay.pro 2026-09-01 15:21:23 +01:00
STORAGE_ARCHITECTURE.md
TEMPERATURE_MONITORING.md
TROUBLESHOOTING.md Align TrueNAS guidance with JSON-RPC runtime 2026-09-01 18:32:39 +01:00
TRUENAS.md Align TrueNAS guidance with JSON-RPC runtime 2026-09-01 18:32:39 +01:00
UNIFIED_AGENT.md Document per-node agent installs for PVE clusters 2026-09-01 06:36:02 +01:00
UNIFIED_RESOURCES.md
UPGRADE_v5.md
UPGRADE_v6.md Prepare v6.4.3-rc.1 release 2026-09-01 21:37:41 +01:00
VM_DISK_MONITORING.md
WEBHOOKS.md Expose stable webhook message keys 2026-08-26 12:04:43 +01:00
ZFS_MONITORING.md

README.md

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

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

Pulse Intelligence

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

Plans and managed access

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

Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.