mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 14:00:29 +00:00
rcourtman
54f623cffb
The Assistant overlay and its backdrop reserved a hardcoded calc(5rem + env(safe-area-inset-bottom)) for a bar that measures 45px. At 375x812 the backdrop ended at y=732 while the bar starts at 767, leaving a 35px band that was neither dimmed nor click-blocked: page content showed through and stayed interactive outside an open modal. The bar's height is content-driven and already includes the safe-area inset via pb-safe, so no caller can hardcode it correctly. Five sites had tried: the Assistant panel, its backdrop, the star banner, and both halves of the .filter-bottom-nav-aware-panel rule, which also carried a derived 6rem. MobileNavBar now publishes its measured height as --pulse-mobile-nav-height and those five sites read it. Publishing happens in onMount rather than the ref, because Solid runs refs before the node is in the document where offsetHeight is 0; reading after mount forces layout and gets the real value on first paint. A ResizeObserver covers content-driven changes and a resize listener covers the xl breakpoint, where the bar swaps between its height and 0 by display alone. The declared :root value is only a pre-measurement fallback and deliberately under-estimates. Over-reserving is what produces the un-dimmed band; reserving slightly less is harmless because the opaque bar paints over it. Verified at 375x812 and 1280x800: backdrop and panel now both end at 767 against a bar top of 767, gap 0; the point 5px above the bar hit-tests to the Assistant panel rather than page content; the filter panel resolves to 45px on mobile; and the star banner's md:bottom-4 still wins at 16px. Adds the regression proofs the shape guard asks for, including an architecture test that fails if any runtime source reintroduces a literal bar height, and records the ownership boundary in the frontend-primitives and ai-runtime contracts.
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.