Requests
Under Consideration
Currently, some files occupy substantial local disk space, becoming unmanageable over time when stored locally. Implementing S3 (compatible) storage can offer a cost-effective solution with enhanced performance. Other software has successfully adopted S3 storage, resulting in significant reductions in local space usage and notable improvements in application performance. We request the integration of S3 storage to optimize resource utilization and enhance the overall efficiency of Blesta.
TL:DR: AWS S3, Wasabi or any other S3 compatible storage to save local files like ticket attachments, etc
I like this idea
If we implement this, it would probably totally replace the "uploads" directory, every file stored in uploads anywhere in Blesta (core + all plugins) would be pulled from an S3 bucket you configure. This could result in a lot of S3 requests, for commonly accessed things like logo, invoice logo/background image, etc. Do you see any issues with that?
Thanks for your reply @Paul.
No, I don't see any issues with that. Usually pulling files from the S3 Provider is free (Wasabi, Backblaze), or cheap (AWS S3)
You can even set a custom domain for the asset url, like assets.yourdomain.com, request don't need to go through your PHP backend. They can go directly to the S3 CDN for public files.
For private files it can auto-generate an access token on demand.
Packages like Laravel Filesystem manage this very well: https://laravel.com/docs/11.x/filesystem
Comments have been locked on this page!