[Feature Request]: Official support for BorgBackup integration

[gitjuice]

Hi, and thanks for your work on this project — the CLI is a great step forward for those of us who prefer automation and terminal-based workflows.

I'd like to request official support for BorgBackup (https://borgbackup.readthedocs.io/) integration.

Why Borg?

Borg is widely used in the Linux/Unix community for encrypted, deduplicated, and compressed backups. It's scriptable, secure, and efficient, and many sysadmins (myself included) rely on it daily for production and personal backups.

What would support look like?

At a minimum:

• The ability to use internxt-cli as a Borg remote repository backend (similar to rsync, ssh, or sftp).
• Alternatively, a FUSE mount option in internxt-cli that would allow Borg to operate normally over a mounted path.
• Or, a borg serve-compatible endpoint or wrapper script.

Benefits for Internxt:

• Attract power users and sysadmins looking for a privacy-friendly cloud backend.
• Increase adoption in automation-heavy environments.
• Add a real-world use case for the CLI beyond just upload/download scripts.

Let me know if this would be considered, and if so, I’d be happy to help with testing or feedback.

Thanks again for your time and work!

[mcdullmedia]

Rclone are still broken even it is officially supported (suppose).
I have no hope on this.

[cbertelli]

Rclone are still broken even it is officially supported (suppose). I have no hope on this.

I think this could be split in two parts:

1. stabilisation of the backend
2. implementation of a new driver for BorgBackup.

For (1), I agree there is space ahead for improvement – I hope existing bugs are fixed quickly (my user's point of view);
For (2), I think contributions are needed to maintain it in good shape for the future.

BorgBackup is written in Python (v. 3.9+); @CrispStrobe implemented the Internxt algorithms in Python with an alternative internxt-cli, so I hope adapting the interface to Borg should not be very demanding.