Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Alternative Storage Provider Support #250

Open
z1pti3 opened this issue Nov 14, 2021 · 0 comments
Open

[Feature] Alternative Storage Provider Support #250

z1pti3 opened this issue Nov 14, 2021 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@z1pti3
Copy link
Owner

z1pti3 commented Nov 14, 2021

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.

@z1pti3 z1pti3 added the enhancement New feature or request label Nov 14, 2021
@z1pti3 z1pti3 added this to the v4.0 milestone Nov 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant