This will save some space on the server by directly upload it to the backup server.
@Webtica No it's not the same, streaming is a different way of uploading the file to the remote 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?
Got the same issue with some big sites. Streaming or chunking would help.
It would also be good to have failed backups removed after x days or something.
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! 🥳
Dennis, is Google Drive one of the ones on the list to do?
Fantastic news Dennis, has been a problem for us on a few site. :-)
Hi Dennis, does this include Digital Oceans Spaces? What you already support?
All S3 drivers stream it now. (So custom S3, AWS S3 and DigitalOcean Spaces).
