snxraven/gnome-jarvis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Update Installer
Rolling release / release (push) Canceled after 6m21s
Details

Browse Source
This commit is contained in:
snxraven
2026-09-11 21:28:44 -04:00
parent 9e76928045
commit bd34ec49aa
5 changed files with 178 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/MIGRATIONS.md
+9 -3
View File
@@ -6,9 +6,15 @@ The user installer keeps application files in
`~/.config/jarvis/qvac.config.json`. Memory, voice references, audit logs, and
generated media remain under their existing Jarvis data directories.
Upgrades replace only the application and extension files. Existing config and
data are preserved. Run `systemctl --user daemon-reload` after installing a new
service file, then restart `jarvisd.service`.
Upgrades stop a running `jarvisd.service`, uninstall the previous GNOME
extension, and replace `~/.local/share/jarvis-qvac` from a staging directory so
leftover files from older versions cannot mix with the new tree. Failed staging
directories next to the install prefix are removed first. Existing config and
data under `~/.config/jarvis`, `~/.local/share/jarvis`, and the model cache are
preserved. If the service was running, the installer restarts it after the
replacement; `--enable` also enables the unit. Run
`systemctl --user daemon-reload` only when you install the service file by
hand.
The uninstall command requires `--yes` and preserves data. Add
`--purge-data` only when the user explicitly wants Jarvis-owned memory, cache,