Is your feature request related to a problem? Please describe.
Currently jimi offers local storage options whereby storage files are ever saved into the database ( ok for small files ) or locally within the data/storage folder. The local storage folder is synced to all cluster members using a HTTP based API. The problem with this is speed when using jimi for package deployment or distribution of large files.

Describe the solution you'd like
As well as the two options already it would be good to expand storage to enable support for S3, NFS and other remote storage locations so that files can be downloaded and accessed on demand instead of syncing them to every node. These solutions should maintain hash in the database and support local caching within temp so that flows are still efficient.

Files that are on external providers should not be included in the sync system as jimi would not be responsible for replicas.