storage
storage copied to clipboard
keystonejs
Hopefully someday they will include this library into keystone as a dependency.
According to our slack talk, it is possible to have storage.js is a part of the dependency in keystone.js in someday and we will need someone to put this bolt and nuts into the keystone and makes it complete. If so there is a list of possible items that we are looking to add into this library as support. Namly the hottest providers in the market in this year 2015 which is listed on abouthome. Feel free to check it out.
- [x] baidu cloud - ready
- [x] Formerly called skydrive, now called OneDrive . there is a cover from fog
- [x] Mega drive, before starting there is npm package I have found in here mega-npm
- [ ] Hive
- [ ] MediaFire
- [ ] Pydio
- [ ] pCloud
- [x] Google Drive is planned. I have found someone did a package for the api and its here google drive api and also fog. Still have not decide with one we should use.
- [ ] SurDoc
- [x] Dropbox is covered from fog
- [x] Box I have found a promising package in here. npm - Box and fog
- [ ] 360 Cloud Drive - hot in china, very popular in the chinese
- [ ] Yankex
- [ ] ADrive
- [ ] hubic
Feel free to add your own if you have a good provider.
are you sure this is storage in the same sense as s3/azure/googleCloudStorage ? off the top of my head I don't believe you could just upload photos programmatically to mediafire (I may be wrong)
I don't see a huge advantage over using yet another wrapper, like 'fog' - especially when it uses almost the same underlaying libraries as our module (our aim is pretty much the same). I'd rather stick with our own implementations using core dedicated libraries like we do for now. Another thing is that fog states that its still under heavy development which is quite weird as the last commit has been made at least half a year ago.
I am about to clean up source code this week, reinvent it in few places and we should have alpha version this week.
For the initial release we should stick with the providers that has been already discussed in Keystone repository and add new on ongoing basis as other users suggest them.
Also - we need to support Storages that can handle ANY File (like above storages mentioned), resigning from filetype-specific providers.
If anyone is interested in covering above libraries, please hold on for a couple of days as I am going to write simple middleware pattern here so community plugins can be kept under different repositories (the main idea is to keep this as slick and simple as possible yet extensible).
@grabbou I am appreciated your vision and aiming. I am too hope that there is a main middleware that we are relay on to make any extensions so that people can easily adding the implementation according to the api doc from the provider.
