mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
065cd2bf37
The Docker containers table now shows whether each container is healthy and how long it has been running. - **State names the problem.** It shows Unhealthy (red) or Starting (amber) for a running container's health check, Exited (139) (red) for a crash, Restarting, and a muted Exited or Paused for a container stopped on purpose, with the full sentence on hover. Before, an unhealthy container read `running` and only its dot was red. The column also disappeared whenever every container was running, so a fleet with one failing health check showed no State column at all. The column now appears whenever any row has one of these states. - **Stale health is ignored.** Docker keeps the last health status on a stopped container (#1724), which made a stopped container's dot read unhealthy. Health now counts only for a running container. A container with no reported Docker state is treated as running when its status is online. - **Uptime column.** From a 900px table, an Uptime column shows the current run, so `0m` or `5m` marks a container that just restarted. v5 had this column. Stopped containers show a dash, and narrower rows keep uptime in the drawer. - **Room for the new columns:** - A single-host table, which is always flat, drops the Host column that repeated one name on every row. - The Ports cell drops the all-interfaces address and the duplicate IPv6 entry, so it reads `23210->8080/tcp`. A specific bind address such as `127.0.0.1` stays, and the hover text, drawer and search keep the full form. - Column weights moved from CPU, memory, ports and networks. - New model tests hold the State words (86px) and the Uptime header (57px) at each layout's narrowest table, alongside the existing Update-control width test. Verification: - Measured every column at nine widths from 390px to 1920px against main, which now includes #2521. Nothing new clips except one more truncated container name at 1000px. Ports overflow per cell drops from 175px to 123px at 1440px. "Exited (139)" fits on a 390px phone. - Checked unhealthy, starting and stale-health states, the single-host view, dark mode and the phone drawer, using edited API data. The receipt is included.
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.