Make it easy to provide alternate storage plugins

Hi,
I'm trying to develop a new plugin for Cloudflare's R2 storage.  Creating the plugin is easy.  When I try to integrate it with eDocman, I can only see specific enablements for S3 plugin.
Would you consider making the storage plugin enablement more generic so that it could work with any storage  offered by a plugin?

This would surely be to your benefit as you could be specific about how the plugins should present the info, so that they would work properly with eDocman.
Then it would be trivial for adding any kind of external storage service, just follow the rules.

Just for info we have developed our plugin  for R2, even though R2 is supposed to be compatible with S3, it doesn't work with your S3 plugin.

Hi,
Thank you for your suggestion and for sharing the information about your Cloudflare R2 plugin.
At the moment, EDocman already supports several online storage integrations, including:
- Dropbox
- Google Drive
- S3
- OneDrive
Because of this, EDocman already has a standardized input/output structure that allows storage plugins to work with different online storage services.
The current storage integration system is not limited only to S3. It was designed to support multiple online storage providers through plugins, as long as the plugin follows the required structure and data handling rules used by EDocman.
Regarding Cloudflare R2, although it is described as S3-compatible, there may still be differences in authentication, endpoint handling, request signing, or API behavior compared with Amazon S3. That may be why it does not work directly with the current S3 plugin.
Best regards,
Dam

Thanks for quick reply Dam, when looking in the layout for Admin Document view, only S3 plugin enables the additional path field? Did not see any others. Do you have development docs for creating additional? We couldn't find any hence the deconstruct on how it worked internally.
is isAmazonS3TurnedOn just legacy naming?