mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 12:42:49 +00:00
rcourtman
b8a0f87e6b
Rebuilds #2432 as one commit on current main. Its branch conflicted with the Tailwind 4 move (#2443) in StackedDiskBar.tsx and DockerTasksTable.tsx; the resolution keeps this change and main's class renames (rounded-sm to rounded-xs). The eight original commits' reasons follow. Read PBS datastore status in the storage vocabulary: The PBS poller reports a datastore as "available", or "unavailable" when PBS returns an error for it. The datastore adapter mapped that string through the generic status mapper, which only knows online, offline and warning, so every healthy PBS datastore showed as "Unknown" in the Storage tab and an unavailable one was not flagged. PVE storage already maps the same vocabulary through its own storage mapper. Share that mapping so a PBS datastore reads online or offline like any other storage. Carry shared PBS storage as one cluster row in the mock estate: The mock emitted each cluster's two shared PBS storages once per node, each with its own usage figure. The real poller folds a shared storage into one cluster-scoped entry, which users asked for in issue 1049, so the demo's Storage tab contradicted the shipped behaviour: ten rows of "west-backup-primary" with different usage and growth on a five-node estate, and a hundred on the public demo. The fixture now carries the merged shape: one row per store with the reporting nodes listed and a cluster-scoped id, offline only when no cluster node is online. Name Proxmox storage types and shared hosts as operators know them: The Storage tab title-cased any storage type it did not map, so the default local-lvm on every Proxmox install read "Lvmthin" and an NFS share read "Nfs". Those types now carry the names the Proxmox UI uses: LVM-Thin, LVM, NFS, SMB/CIFS, iSCSI, ZFS, BTRFS, GlusterFS and ESXi. A storage the poller merged across the cluster showed the synthetic node marker "cluster" as its host. It now reads "Shared", with the reporting node count when the storage lists its nodes. Carry PMG metadata on REST-mapped resources: The Mail Gateway table reads resource.pmg. The REST-to-Resource mapper set every other provider facet at the top level but kept pmg only under platformData, so a row sourced from the REST snapshot rendered every PMG column (version, nodes, mail in, spam, virus, quarantine, queue, deferred) as a dash. The websocket snapshot carries pmg at the top level, so the table filled in only when a websocket row happened to replace the REST row; on a fresh load the two transports race, and about half the loads stayed blank for good. The mapper now carries pmg like the other facets, and a test pins it. Label multi-disk hosts with their fullest disk in Bars mode: A host with more than one agent-reported disk draws its Disk cell as one micro-bar per disk and no figure, while a single-disk host shows a percentage and Trends mode shows one for every host. Bars is the default view, and most Proxmox nodes have at least local-zfs beside a data pool, so the question "which node is running out of space?" had no at-a-glance answer for the rows that matter most; the column's own sort key was a number the cell never showed. The cell now carries the fullest disk's usage beside the micro-bars. Every bar keeps equal weight and no disk is named in the row; the mount and the per-disk breakdown stay in the title and the tooltip. Carry source status, action readiness and technology on REST rows: The same race that blanked the Mail Gateway table applies to three more fields the API returns: sourceStatus, actionReadiness and technology. The REST mapper set sourceStatus only under platformData and dropped the other two, while websocket rows carry all three at the top level. Docker container lifecycle actions read sourceStatus and actionReadiness to decide refusals, storage rows read sourceStatus for freshness, and search suggestions and the assistant context read technology, so whichever transport won a fresh load decided whether those consumers saw the data. The mapper now carries all three, the REST type declares the two it omitted, and the PMG mapping test pins them. Fit the Docker containers table and read Swarm state as words: On a 1280-1536px laptop window the containers table clipped its short values: the engine read "docker 2…", host names lost their tail, and the Update control itself was cut off, while the percentage-only CPU and memory bars had room to spare. The compact widths now give those columns their share. On a phone the row dropped to "runni…" with an unreadable Restarts header beside a wrapped Update button; the phone row now keeps container, state, CPU, memory and Update, and the restart count stays in the row expansion until mobile width. The images table on a phone showed "Not c…" for the update verdict and a clipped host; it keeps image, size and update check there and defers host and consumers to the expansion. Swarm services showed the rollout state as the raw token "rollback_started" and Swarm tasks showed a raw RFC3339 stamp with microseconds as their start time. The state reads as words and the start as an age, with the raw values in the title. Keep demo Docker container names unique per host: The demo scenario reused its curated container profiles for a second round on hosts with more containers than profiles, so a host showed two running "customer-portal" rows and every image's "used by" list read "customer-portal, customer-portal". Docker refuses two containers with one name on a host, so the duplicates read as a bug to anyone evaluating the demo. A reused profile now takes a numbered suffix. Contract-Neutral: Storage type labels, shared-host label, REST mapper carrying fields websocket rows already carry, Bars-mode disk label and Docker column fits are presentation and mapping only; owning unified-resources and storage-recovery clauses updated; no frontend-primitives primitive, API or runtime boundary change
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.