Feature #11725
Dashboard needs a plugin manager
| Status: | Needs More Information | Start date: | 01/04/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Keywords: | Affected URL: | |||
| Branch: | Affected Dashboard version: | |||
| Votes: | 0 |
Description
…because rake tasks are an unacceptable way to install and manage Dashboard plugins. This is also an important part of making Dashboard act more like a framework than an application.
History
Updated by Daniel Pittman 4 months ago
I think this needs user stories and other supporting material before we land at that conclusion, right?
I am not certain, for example, that this is a user configurable thing?
Updated by Daniel Pittman 4 months ago
- Status changed from Unreviewed to Needs More Information
Updated by Randall Hansen 4 months ago
Daniel Pittman wrote:
I think this needs user stories and other supporting material before we land at that conclusion, right?
I am not certain, for example, that this is a user configurable thing?
It’s certainly an admin-configurable thing. Anyone with root on the server can enable/disable plugins. If we want to push more admin features into common (e.g., GUI) tools and away from one-off hacks (e.g., rake tasks), then this is the way to go.
Updated by Jason Antman 4 months ago
Disclaimer: my ruby skills are practically nonexistent. I’ve run Rails stuff (puppet/dashboard and redmine) but nothing more.
I know we’re talking PHP vs RoR, but if you look at some of the web apps that are well known for their large plugin ecosystems, such as WordPress, most of them either support auto-loading of plugins (by simply dropping them in the correct directory), or auto-discovery and then enabling them through the GUI. At about the worst, there’s MediaWiki which just needs a “include(pluginpath/pluginclass.php)” in one file.
I really like where Dashboard could go. But I also think that providing as simple a plugin experience as possible, and encouraging third-party plugin development, should be a key priority.