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

Do not activate plugin on require #5

Merged
merged 1 commit into from
Apr 24, 2016

Conversation

tvdeyen
Copy link
Contributor

@tvdeyen tvdeyen commented Apr 23, 2016

Bundler requires all gems automatically.

This plugin tend to activate itself on the :default Dragonfly app if it gets required, while in the README is noted that one has to activate it manually.

Activating this plugin explicitely on the preffered Dragonfly app is better than magically activating it.

Bundler requires all gems automatically. This plugin tend to activate
itself on the default Dragonfly app, while in the README is noted that
one has to activate it manually.
Activating this plugin explicitely on the preffered Dragonfly
app is better than magically activating it.
@tomasc tomasc merged commit 19395e2 into tomasc:master Apr 24, 2016
@tvdeyen tvdeyen deleted the do-not-activate-plugin branch April 24, 2016 22:13
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

Successfully merging this pull request may close these issues.

2 participants