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

Split hyperpotamus plugins into separate modules. #11

Open
pmarkert opened this issue Nov 18, 2016 · 0 comments
Open

Split hyperpotamus plugins into separate modules. #11

pmarkert opened this issue Nov 18, 2016 · 0 comments

Comments

@pmarkert
Copy link
Owner

I'd like to leave the base hyperpotamus engine as this module and then split-out all/most of the plugins to separate modules. I would want to have a few "collection packages" that bundle sensible groups of plugins together and then some of the heavier-weight (and especially un-safe) plugins could be in separate packages. This would allow/support a few benefits:

  • New plugins can be added without having to bump the base hyperpotamus version.
  • Updates to existing plugins can be versioned separately
  • Smaller (lighter-weight) deployments can be tailored that limit what plugins are included
  • Makes it easier for the community to add and support plugins
  • Separation of safe/unsafe plugins from an installation standpoint.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant