mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
5186d4c560
Follow-up to rcourtman/Pulse#2477. **Docker containers get the bulk editor** The strongest demand for saved links (#1556, #624) came from Docker users, but the editor only reached Proxmox and vSphere guests. The Docker containers table header now has the same **Edit links** panel, worded for containers. - Rows are keyed through `toDiscoveryConfig`, the container drawer's own metadata target, so bulk and drawer saves read and write the same `app-container:<host>:name:<name>` record. This includes Docker running inside Proxmox LXCs. - The editor now takes a source. Workload tables pass live guests, so the row model still loads only with the panel. Other tables pass ready-made rows. - The Docker table lazy-loads the trigger. Without that, Rollup merged it into the chunk the Docker and workloads pages share, renamed that chunk, and broke the `DrawerDiskListCard` bundle budget. **Read-only tokens no longer see edits that would fail** Metadata writes require `monitoring:write` for API-token sessions (the backend's `EnsureScope`). Browser sessions always pass, because metadata routes have no role check. A kiosk-style `monitoring:read` token saw edit controls that every save refused with 403. The session store now mirrors the gate from the security status `tokenScopes` (`sessionCanWriteMonitoringMetadata()`): - the bulk editor's **Edit links** button is hidden for such sessions; - the shared web-interface field shows the saved URL with open and copy, plus a one-line explanation, but no input, Save, Remove, or "Use this" suggestion. **Fewer refetches** Saves now dispatch their metadata-changed events together after the writes. `useUnifiedResources` coalesces onto one in-flight refetch, so a bulk save costs two resource refetches whether it changes 2 links or 4. Before this, it cost one per link. **Verification** - Private mock stack, Docker page and Proxmox page, at 1280 and 375px. - Real token sessions with the admin bypass off: a `monitoring:read` token sees no edit affordances, and a `monitoring:read+write` token saves a container link. - Receipt: `frontend-modern/browser-verification/e8946b639f30703c.json`. - Production build: `WorkloadsSurface` 69.08 kB, `Docker` 28.56 kB, `DrawerDiskListCard` unchanged; no violations. - Full frontend lint, plus 841 test files (15,618 tests) across features, hooks, components and stores.
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.