💾 Archived View for bbs.geminispace.org › u › Supernova › 4975 captured on 2023-11-14 at 09:20:17. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Re: "Feature request: export user data via cli arg"
Oh, is that true @skyjake, the .config/lagrange files may not always be up to date?
Aug 31 · 2 months ago
@Supernova Many of the files are updated immediately when a change occurs in the app (bookmarks, identities, trusted certs, visited, prefs.cfg — saving of open tabs and UI state is coming in v1.17). When the app is closed, the full navigation history content cache is additionally written to state.lgr.
So the data that is included in the export archive should always be up to date.
You should be aware that multiple instances of the app cannot safely use the same runtime directory. If you run multiple instances, you need to manually override the runtime directory in the extra instances.
🔭 Supernova · Aug 31 at 21:03:
@skyjake, thanks for the info. So I think a cronjob with a tar command should be enough for an automated backup. Maybe history wouldn't be up to date. Or close the app, then run the backup and reopen it again.
My use case was actually for syncing across multiple devices. Using syncthing the .config/lagrange folder could be synced in real time. Usually I would only be using one device at a time so file updates should propogate without conflict. But if for example the bookmarks file was changed on another device while Lagrange was running, would it load the new changes?
Feature request: export user data via cli arg — It would be really nice if we had the ability to use something like `lagrange --export-user-data` instead of having to export it from the app. The reason I would like such a feature is so that I could have a scheduled task export the data to my sync directory periodically. This would make it easier to keep Lagrange in sync on my devices.