mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-19 21:06:09 +00:00
Logs: every log in app-private storage, shared as one scrubbed zip
Session folders, tools/ and the stores' log now live in files/logs (LinuxRuntime.logDir) instead of Download/DroidDeck. The files directory is bound into every session at the same path, so the session script and the guest tools write there as before. Thirty sessions kept; the Logs switch off still means a cache folder deleted at session end. Game save backups stay public. On the first start, session folders, tools/ and loose .log files move from Download/DroidDeck into files/logs (rename, else copy and delete; a failure leaves the item where it was). Saves/ and anything else there is never touched, and the folder is not read again. Share logs builds one zip in cache/share/: the session folder, with the last seven days of stores/ and tools/. Every text file goes through LogRedactor.redactForShare on the way in - the existing rules, plus URLs without query, fragment or userinfo and with token-bearing path segments blanked, __token__ / f_token / hdnts / OAuth code= values, and Authorization / Cookie headers - so a file written before a rule existed is clean in the zip. The zip goes at the next share or app start. No existing scrub is relaxed. The file manager's Session logs shortcut opens files/logs.
This commit is contained in:
1 parent
8e1a676f19
commit
56bc2cd3f7
20 files changed
+264
-69
No files matched your search
@@ -22,7 +22,7 @@ The script then unpacks them without hooks and checks what the binaries link. Li
|
||||
the Desktop package normally brings (PyGObject, json-glib, fuse3 and others) are fetched too,
|
||||
but only when their files are missing. Flathub is added as a per-user remote from a copy of
|
||||
its `.flatpakrepo` carried in the script, so that step needs no network. Every store command
|
||||
writes its output to `Download/DroidDeck/flatpak-<verb>.log`, next to the session logs. The
|
||||
writes its output to `files/logs/tools/flatpak-<verb>.log`, next to the session logs. The
|
||||
setup script also puts Flatpak's own error text in the failure message the app shows.
|
||||
|
||||
## bubblewrap without namespaces
|
||||
|
||||
Reference in new issue
Block a user