alex
900a8e47a5
Disable duplicate refresh requests and show in-progress feedback while Git mount sources are refreshed.
26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# Live Git Config Mount Refresh
|
|
|
|
## Why
|
|
|
|
Git-backed Config Profile mounts are currently cloned per instance. Their content cannot be refreshed consistently for running sessions, and writable container mounts can dirty the checkout.
|
|
|
|
## Change
|
|
|
|
Move Git Config Profile mounts to profile-scoped canonical host clones. Bind the already-mounted directory sources read-only into compatible instances and refresh a stable branch/ref checkout in place under a per-clone lock.
|
|
|
|
## Scope
|
|
|
|
- Canonical clone identity: profile, normalized remote, requested ref, and credential scope.
|
|
- In-place refresh for existing directory mounts only.
|
|
- Explicit outcomes for live refresh, restart-required topology changes, and refresh failures.
|
|
- Read-only container Git config mounts.
|
|
- An in-progress indicator that prevents duplicate refresh requests in desktop and mobile Config Profile views.
|
|
|
|
## Out of scope
|
|
|
|
- Writable shared Git configuration mounts.
|
|
- Global cross-user clone sharing.
|
|
- Live mount-topology changes, direct-file mappings, or glob match-set changes.
|
|
- Atomic all-files revision switching for processes already reading the mount.
|
|
- Automatic refresh of an editor buffer that has already loaded a mounted file.
|