mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-23 20:25:56 +00:00
rcourtman
b12af35847
`bg-base` has rendered nothing since the `base` colour alias was removed (it also coloured the `text-base` font-size utility). Tailwind 4 ignores unknown colour classes without warning, so about 85 uses were transparent. On the page background that looked the same. Inside cards it did not: - command, JSON and XML blocks lost their wells (External agents, Agent Doctor, installer, update guide, Ollama, SAML preview, setup wizard); - the Patrol mode segmented control showed its selected option as a white chip on a white track; - the branding header preview vanished into its card; - the Dead Man's Switch "Not configured" pill read as plain text; - the alert bulk-selection bar showed white count text on a see-through pill. What changed: - New `@utility bg-page` (the page backdrop, deliberately not a theme colour) for wells inside surface cards. - `bg-surface` for blocks on a surface-alt body (resource drawer JSON, correlation and policy cards) and for the floating bulk bar; `bg-surface-alt` for the muted Card tone; `hover:bg-surface-hover` for drawer buttons whose hover did nothing. - The class is dropped from page shells that sit directly on `<body>`, which already paints the page colour. - Command text that assumed a dark well (`green-400`, `blue-400`, `emerald-400`, `slate-300`) gets light-mode shades so it stays readable. - `App.architecture.test.ts` fails if a runtime class uses `bg-base` again or a theme colour named `base` comes back. Verified on a private mock stack before and after, in light and dark, at 1440px and 390px; details are in the browser receipt. A few surfaces can't be reached with mock data (the drawer change history and its coloured buttons, Quick Security Setup, the profile-suggestion JSON, the Patrol tool-call trace). Their new tokens follow the same container rules, and the drawer button hover was measured with the exact classes in the live drawer.
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.