mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-23 20:25:56 +00:00
rcourtman
986cead30c
Stacked on #2723 (its one commit is the parent here). Whichever lands
first, the other still merges.
## Problem
Selecting a Workloads row called `capturePendingAppShellRestoreTop()`,
which staged the `.app-scroll-shell` position for `App.tsx` to restore
on the next route change. That made sense when row focus wrote
`?resource=` into the URL. 86ac84f68e made selection local, but the
capture stayed. So the staged position now waits for whatever route
change comes next. The same-path route-state scheduler only re-stages
from a scrolled shell, so at scrollTop 0 the old value survives.
Reproduced on a mock estate (embedded build of main, /proxmox/overview,
1440x900 and 390x844), with every scripted `scrollTop` write on the
shell recorded:
| Steps | main | this branch |
| --- | --- | --- |
| Open a guest drawer at scrollTop 3000, scroll to 0, set Type to VMs |
URL becomes `?type=vm`, then the shell jumps 0 → 3000 (74 ms later on
desktop, 126 ms on phone) | stays at 0, no scripted write |
| Same scroll path, no drawer | stays at 0 | stays at 0 |
| Drawer, then filter changed at scrollTop 500 | stays at 500 (the
scheduler re-stages) | stays at 500 |
| Drawer, then Proxmox Storage sub-tab or Docker tab | 0 (destinations
are shorter than the stale offset) | 0 |
## Change
- `useWorkloadSelectionState.ts`: drop the capture. Row focus already
holds its place through `preserveScrollableAncestorVerticalOffset`;
opening a drawer still leaves the shell at 3000 with the URL unchanged.
The now-identical `setSelectedGuestIdState` folds into
`setSelectedGuestId`.
- `appShellScrollRestoration.ts`: delete the capture helper, which has
no callers left, and its branch-coverage test. `routeStateNavigation.ts`
is now the only producer, and it stages right before it navigates.
- A regression test in `useWorkloadSelectionState.test.ts` toggles a row
at 3000, returns to 0 and runs a same-path filter write. It fails on the
parent with `expected 3000 to be null`.
- Contract prose in performance-and-scalability and unified-resources no
longer describes the old capture handoff.
## Verification
- Before/after browser probe at both widths on pulse-dev. A `?resource=`
deep link still opens and reveals the drawer, closing it keeps the
position, and there were no page errors. Receipt:
`frontend-modern/browser-verification/b3c60348af17e8cc.json`.
- prettier, eslint and `tsc --noEmit` are clean.
- Targeted vitest: 556 files passed. `docsLinks.test.ts` timed out at
host load ~76 and passes on its own (104/104 across the five related
files).
- Full pre-commit and pre-push batteries passed.
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.