This will save some space on the server by directly upload it to the backup server.
The current backup method generates big backup files that are stored in the .ploi folder. If a backup fails the failed file remains sitting in that folder. When a few backups fail it might end up in filling the storage completely.
Also if the total backup size is bigger than the free space you cannot make a backup via Ploi at all right now.
If you want a better solution you need to do something with chunks imo. Only streaming won't really help.
Is the current backup method incremental? Or do you get a full file of the complete site every time you take a backup?
I hope you are talking here about incremental backups. That's really required ala JetBackup.
It would be good if one could also limit the amount of concurrent Streams, as for example some storage providers like Hetzner Storage Box only allow X amount of concurrent connections
This is coming, no more bloaty files on your server: direct uploads to the external driver 🥰
OK, quick update: The S3 and Custom S3 uploads are now streamed, they do not take any space up on your server anymore. Other drivers will be next! 🥳
Hi Dennis, does this include Digital Oceans Spaces? What you already support?
Sadly, I have to turn this down.
I tried many ways, the way Ploi creates backups doesn't work well with zipping/tarring and streaming for some reason. (For example, SQL files are called - inside a ZIP or TAR file which is strange, it still holds the content) It just doesn't play nice when streaming directly into a archive file and sending it to the remote driver.
Other than that, most drivers, don't even allow this. We'll look at this at a later stage again that we could do it driver-specific, but for now, no go sadly.
