I see a ‘Launch at Startup’ but nothing like ‘Start Minimized’ or ‘Start in System Tray’.
Ref:
I created a file system repo.
I applied my global policies.
eg: kopia policy set --config-file="$conf" --global --compression="zstd-better-compression"
I restart the appimage.
I create another file system repo.
I restart the appimage.
I close all the Kopia windows being puked up on my screen.
I check the first file system repo.
Applied policies are present.
I check the second file system repo.
No applied policies are present.
I reapply global policies using the --config-file="$conf" of…
Note: a missing repository.config is responsible for this even if there are existing custom file names for other repositories present. The esteemed minds behind Kopia hard coded a conditional file name check but didn’t extended it to seek other out other .config or just ignore that ‘need’ for something so trivial yet so damn annoying.
Related:
CLI/AppImage
All repositories have a ${HOME}/.config/kopia/$customRepoNameHere.config. Following this example from the Kopia docs to ensure no interfering ID10T errors, I execute
kopia policy set --global --compression="zstd-better-compression"
Result:
kopia policy set --global --compression="zstd-better-compression" || nowutc
ERROR open repository: repository is not connected. See https://kopia.io/docs/repositories/
20250430T055955UTC
However after setting a repository.config:
ls -l ${HO…
I’m relatively new to Kopia and initially could not understand how the Kopia UI app interfaces with multiple repositories. Eg, in windows, when I right click on the Kopia icon in my taskbar, I was seeing multiple repos listed, some of which it could not connect to.
I couldn’t find this documented, but after playing around for a while and reviewing log files, I figured it out & wanted to document my findings. This is based on my testing on the Windows platform:
When you start up KopiaUI, it …