Describe the solution you'd like
This issue proposes enhancing the Attachments plug-in to support alternative storage mechanisms instead of relying solely on local file storage.
Currently, files attached to entities such as customers, orders, and products are stored on the user’s local machine inside the plug-in directory. This creates a limitation where files cannot be accessed from different machines, making collaboration and multi-device usage difficult.
We should introduce a mechanism that allows users to select and configure alternative storage providers, such as Google Drive, OneDrive, Dropbox, FTP, or similar services. The attachment system should then store and retrieve files using the selected provider, while keeping a consistent abstraction for the rest of the application.
This enhancement will:
-
Make attachments accessible from multiple devices
-
Reduce reliance on local storage
-
Enable a more cloud-like experience
-
Allow flexible storage strategies depending on user needs and infrastructure.
Alternatives you've considered
No response
Additional context
No response
Describe the solution you'd like
This issue proposes enhancing the Attachments plug-in to support alternative storage mechanisms instead of relying solely on local file storage.
Currently, files attached to entities such as customers, orders, and products are stored on the user’s local machine inside the plug-in directory. This creates a limitation where files cannot be accessed from different machines, making collaboration and multi-device usage difficult.
We should introduce a mechanism that allows users to select and configure alternative storage providers, such as Google Drive, OneDrive, Dropbox, FTP, or similar services. The attachment system should then store and retrieve files using the selected provider, while keeping a consistent abstraction for the rest of the application.
This enhancement will:
Make attachments accessible from multiple devices
Reduce reliance on local storage
Enable a more cloud-like experience
Allow flexible storage strategies depending on user needs and infrastructure.
Alternatives you've considered
No response
Additional context
No response