mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-10 02:25:56 +00:00
rcourtman
a4d37447a0
Discovering Docker inside Proxmox LXC guests previously required an undocumented environment variable plus a hand-edited systemd unit, which is how the surface kept shipping invisible. The opt-in is now a persisted system setting with an admin-only toggle in Settings → System → General, presented as its own "Docker in Proxmox LXCs" card under the existing Docker/Podman updates card, with the requirements (node agent with command execution) and data-collection bounds stated inline. The setting rides the admin-gated system settings endpoint (RequireAdmin + settings:write, matching every other server-wide toggle). Flipping it persists first, then applies to the runtime config and fires a reconfigure hook so the router rebuilds the monitor's Docker checker and inventory collector immediately — no restart. PULSE_ENABLE_PROXMOX_GUEST_DOCKER_INVENTORY remains authoritative: when set it locks the toggle (EnvironmentLockBadge in the UI, HTTP 400 from the API), and an unrelated settings save can never clobber the runtime value. The opt-in guardrail test now pins the settings path, the env lock, and the persisted field. Installer and node setup-guide callouts now point at the toggle first with the environment variable as the locking override, and the docs, their public mirrors, and the agent-lifecycle subsystem contract say the same. New i18n strings shipped for en/de/es. Verified live in mock mode: toggle off/on from the UI drives the collector teardown/setup log lines, the value survives a server restart, and all three touched surfaces render at desktop and mobile widths (receipt in frontend-modern/browser-verification.json).
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.