Thomas Waldmann 9e6d90754e remove remainders of append-only support ... 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.		2025-04-28 18:55:15 +02:00
..
automated-local.rst	docs: modify docs for automated backup to append to SYSTEMD_WANTS rather than overwrite	2025-01-19 14:41:52 +01:00
central-backup-server.rst	Update repository URLs in docs to use new syntax	2024-09-11 22:03:59 -05:00
hosting-repositories.rst	remove remainders of append-only support	2025-04-28 18:55:15 +02:00
image-backup.rst	docs: borg commands updated with --repo option, fixes #8550	2025-04-01 17:28:57 +02:00
non-root-user.rst	docs: remove tabs	2024-02-25 12:14:52 +01:00
pull-backup.rst	remove remainders of append-only support	2025-04-28 18:55:15 +02:00