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

Proposal: Remove "auto-finding" of Plugins in Favor of the Plugin Manager #1616

Open
markbates opened this Issue Mar 5, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@markbates
Copy link
Member

markbates commented Mar 5, 2019

The plugin manager system, added in buffalo-plugins v1.1.0, added a config/buffalo-plugins.toml file that scopes the plugins Buffalo will see to those listed in the file. There are several advantages to this:

  • Performance - with the plugin list pre-determined we don't have to go scanning the user's system for plugins.
  • Easier for teams - teams can easily see, and install, the plugins for any particular application.

I would like to propose that we remove support for scanning of plugins on a user's system, and, instead, enforce the use of the plugin manager system.

In addition to the advantages listed above with the plugin manager, it will help us to cut down on the number of tickets, such as #1614.

The confusion of having two ways to install, and locate plugins, has caused many of these tickets.

@markbates markbates added this to the v0.15.0 milestone Mar 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.