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

Put extra storages out of the botkit #62

Closed
tilap opened this issue Dec 31, 2015 · 4 comments
Closed

Put extra storages out of the botkit #62

tilap opened this issue Dec 31, 2015 · 4 comments
Labels

Comments

@tilap
Copy link

tilap commented Dec 31, 2015

Hi,

I'm happy to see the 0.0.5 release (not tagged?) with many other storages.
However, most of them need extra packages (monk, ...) that are not is the botkit package.json file.

So when installing, it does not work.
And if you had them all in the botkit package.json, it will install lots of useless packages.

What about keeping only the "jfs" as default (light) and move the others in other npm packages like botkit-storage-mongo, botkit-storage-redis and so on?

@robguilfoyle
Copy link

Would it make sense to ship with a REST storage and a local store, then bring the others in as packages?

@RafaelCosman
Copy link
Contributor

@robguilfoyle That sounds reasonable too.

@tilap and @robguilfoyle, I've been discussing this with @benbrown and it seems like a good move. Major kudos to either of you if create the botkit-storage-* npm packages!

@anonrig
Copy link
Contributor

anonrig commented Jan 4, 2016

We're moving all of the storages into seperate repositories.

Thank you for your response!

@anonrig anonrig closed this as completed Jan 4, 2016
@christophehurpeau
Copy link

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants