Presumably English only, like so much of Duplicati outside of some fortunate program strings.
Still being in a forum battle with the oddities of the AUR (Arch) package and its unusual setup reminds me that there are third party packages and automatic updaters that may break as we change things or require manual steps.
There’s also RuntimeIdentifier (has a mention in Issues) and OSDescription, if they’d help any.
Might work. User would have to know their system somehow, so might need to run OS queries.
That’s the challenge of high flexibility I meant. They can also use various combinations of those.
I don’t know if the migration document has to follow the same format, but it must cover all cases. Installation itself is simpler, now that there aren’t updates everywhere, but stop everything first…
I actually wasn’t sure the CLI used to check each run (update server hammer). It used to be that:
--auto-update (Boolean): Toggle automatic updates
Set this option if you prefer to have the commandline version
automatically update
* default value: false
I agree it’d be good to allow that. I don’t know if the DB version bump is still in the plans though.
Preventing accidental runs of old code has merit, but needs an escape path, if run is intentional.
“full manual deletion” meant remove the install folder, which is where portable mode database is.