6b5bc6938c
0.9.12 derived the running state from the sentinel file, which the host watcher consumes BEFORE update.sh runs — so a reload mid-update showed nothing. Store an 'update in progress' marker (with the base version) in the cache (Redis in prod) instead: it survives both the reload and the app rebuild. On load, mount() resumes the 'running' notice + polling, or — if the running version has already moved past the base — announces completion and clears the marker. 15-minute TTL backstop so a failed update can't wedge the banner. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| Console/Commands | ||
| Events | ||
| Http | ||
| Jobs | ||
| Livewire | ||
| Models | ||
| Notifications | ||
| Providers | ||
| Services | ||
| Support | ||