Refactor modMediaSource, modFileMediaSource and modS3MediaSource to use Flysystem. Flysystem abstracts the S3 to allow MODX to only focus on configuration and implementation. Additionally allow MODX to easily use any of the following: Azure, Copy.com, DigitalOcean Spaces, Dropbox, FTP, GridFS, Memory, Rackspace, ReplicateAdapter, SFTP, WebDAV, PHPCR, ZipArchive or write your own adapter.
N/A
Legacy AWS S3 code must be updated to use composer.
Keep the modMediaSourceInterface class as close as possible to avoid breaking ExtJS. Potential effected files:
MODX 3.0+ version
FYI I will be working on a PR for this soon.
That will be great! I was able to get an sftp source that could actually connect and list files, but every example I looked at was done so differently that it never got any further.
I would like to use visibility instead of chmod, any objections? Would only be public or private.
In the case of a local filesystem, visibility would be an abstraction over the top of file permissions I assume? What's the main benefit? To simplify it?
@digitalpenguin
Visibility is the abstraction of file permissions across multiple platforms. Visibility can be either public or private.
I think the reason is that nearly no adapters have something that can compare to chmod, except traditional file systems.
Done in 3.0
Most helpful comment
FYI I will be working on a PR for this soon.