mirror of
https://github.com/borgbackup/borg.git
synced 2026-02-15 00:34:38 -05:00
9e6d90754e
Some features like append-only repositories rely on a server-side component that enforces them (because that shall only be controllable server-side, not client-side). So, that can only work, if such a server-side component exists, which is the case for borg 1.x ssh: repositories (but not for borg 1.x non-ssh: repositories). For borg2, we currently have: - fs repos - sftp: repos - rclone: repos (enabling many different cloud providers) - s3/b3: repos - ssh: repos using client/server rpc code similar as in borg 1.x So, only for the last method we have a borg server-side process that could enforce some features, but not for any of the other repo types. For append-only the current idea is that this should not be done within borg, but solved by a missing repo object delete permission enforced by the storage. borg create could then use credentials that miss permission to delete, while borg compact would use credentials that include permission to delete. |
||
|---|---|---|
| .. | ||
| make-testdata | ||
| shell_completions | ||
| borg.exe.spec | ||
| errorlist.py | ||
| fetch-binaries | ||
| glibc_check.py | ||
| make.py | ||
| msys2-install-deps | ||
| sdist-sign | ||
| sign-binaries | ||
| upload-pypi | ||