mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
aed2f6c17d
Saved web-interface links make Pulse a quick way to reach the service a guest runs, but each link had to be typed into one guest drawer at a time. This adds one place to set many at once. It ships as a named bet with no external ask behind it yet. **What users get** - An **Edit links** action in the workloads table header. It appears on the Proxmox and vSphere guest tables, which share that surface. - A panel listing every guest in the current filtered view (node selection and filters carry over). Each row shows the guest's type, ID, node, its saved link, and an IP-based placeholder. - An **All / Without a link** filter, a count of guests that have a link, and one Save for every change. Clearing a field removes that link. - Invalid links block the save with the shared validator's message on their row. A failed save stays on its row. Closing the panel keeps unsaved drafts, and the trigger shows "(unsaved)". - Read-only sessions do not see the action. **How it fits** - Saves go through the existing guest metadata API and metadata-changed event, the same path as the drawer field, so the table updates at once. - `getWorkloadGuestMetadataRecord` is now the single lookup for a row's saved link, in both the table and the editor. - Editor rows only follow live inventory while the panel is open, and they keep unchanged row objects across ticks. A closed editor adds no per-tick work, and an open one never remounts the input being typed in. `WorkloadsSurface.performance.contract.test.tsx` pins this. **Verification** - Private mock stack at 1280, 1024 and 375px, covering node scope, filters, invalid entry, add, correct, remove, and close and reopen. Receipt: `frontend-modern/browser-verification/743cc04a20d534ac.json`. - 13 new tests in `workloadWebLinksModel.test.ts` and `WorkloadWebLinksDialog.test.tsx`. - Full frontend lint, plus `src/features`, `src/hooks`, `src/__tests__`, `src/components/shared`, `src/components/Workloads` and `src/components/Storage`: 515 files and 8,675 tests pass.
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.