Commits
mainly was a problem for those declaratively managing configuration with home-manager (including myself) where the agenix env files didn't exist yet, locking up the entire program...
- track tray state by profile name
- move runtime flags into the cli so they appear in help and shell completions
- consolidate backend retry handling
- make `--system` linux only
- other improvements
should always keep the edit actions enabled even if the files are read-only, in case the user just wants to look at the config
mainly improving consistency between the daemon/cli and gui
also improved some variable and function names to be cleaner / fit better with what their actual purpose is
for parity with GUI
- refresh only affected profiles instead of everything which i noticed was very slow with my onedrive rclone repo
- avoid duplicate profile state collisions
- clean scheduler handling
- fix up mount - as my onedrive rclone repo is slow, mount was cancelling before it could even load
- various refactors
now self-managed restic is supported on windows and linux as a fallback if not found in PATH. will remain unsupported on darwin due to macos security killing the restic process randomly
this reverts commit 050127f50d6d84e71bd4d9f0feb5168a48ef2932.
for running with the same configuration/state as the systemd service
i might consider making this windows-only in the future
might as well since we already have the library available
no need to have this anymore. this was something i included when we had the restic management stuff on macos, which was causing macos's security to trip up and kill the process. this did not fix it
index shifts when profiles are
reordered/added/removed while the app is running, causing state to attach to the wrong profile.
also i merged repoStatus + last-backup query into one restic call (snapshots --latest 1) when schedule_display is "last", cutting redundant round-trip on startup for slow backends. (for example, i was having this issue with my rclone onedrive backend taking forever to query and sometimes failing even)
probably not needed, figured out what the actual issue i was having was
also fix up services to work properly
index shifts when profiles are
reordered/added/removed while the app is running, causing state to attach to the wrong profile.
also i merged repoStatus + last-backup query into one restic call (snapshots --latest 1) when schedule_display is "last", cutting redundant round-trip on startup for slow backends. (for example, i was having this issue with my rclone onedrive backend taking forever to query and sometimes failing even)