This project is archived and is in readonly mode.
An extensible API for plugin management
-
Daniel Schierbeck
I've pushed the first bits of code to a GitHub branch. It currently supports installing through Git checkout and Git submodule.
-
Chad Woolley
This sounds like a great idea. Just yesterday I was getting annoyed about how hard plugin dependencies are to manage compared to gems. Dependency hell....
Please provide some mechanism to specify versions or branches of plugins - either a Git revision number, or a branch.
The hook approach for #update and #remove sounds great as well. Ideally, this facility would be completely decoupled from the rest of Rails (especially the config/initialization/environment), so it could be done as part of app startup from config/preinitializer.rb. That way, your piston/braid/giternal config could be leveraged to automatically bring the plugin up to the version you want.
-
Bounga
Chad: That's what we thought about, all SCM plugins should be loaded automatically and system-wide without having to tweak the config files.
-
Bounga
Chad: and yes, revision, branch and all these things will be handle by the manager.
-
Pratik
NOTE : Update Rails::TemplateRunner to make use of script/plugin features. Git submodules for an example
-
Ryan Bigg
Is this still valid?
-
Ryan Bigg
- State changed from new to stale
- Importance changed from to
No updates since my ping in April, closing.
-
Ryan Bigg
Just a little update too: I would say this is handled fairly enough by Bundler now by using the
gitcomment in Gemfile. If you want to use a specific version of a plugin, it's best practice if it was a gem.