Very interesting Jeff :) It would certainly be good if when you tried to install an engine, it checked for the engines plugin and installed it if necessary - fancy coding this up as a patch to the engine generator and submitting it?
- james On 4/4/06, Jeff Lindsay <[EMAIL PROTECTED]> wrote: > I just figured out a pretty cool way to automate the installation of > engines (or well, any kind of plugin)... > > Plugins now have an install.rb that hooks into the plugin installation > process. You can make a new plugin with just this file, called > my_installer for example, and then do something like this in it: > > require 'commands/plugin' > # install the engines plugin > Commands::Plugin.parse! ['install', > 'http://svn.rails-engines.org/plugins/engines'] > # install some engines > Commands::Plugin.parse! ['install', 'http://my-cool-engine'] > Commands::Plugin.parse! ['install', 'http://my-other-cool-engine'] > # install another really cool plugin ; ) > Commands::Plugin.parse! ['install', > 'http://progrium.com/svn/vantage/trunk/widgets'] > # get rid of the installer > Commands::Plugin.parse! ['remove', 'my_installer'] > > Now if you put this up somewhere, you can install all these things > into a new app with: > > $ script/plugin install http://example.com/svn/my_installer > > I imagine you could do a lot of other cool stuff this way! Let me know > if this is already a well known practice or something. :P > > -- > Jeff Lindsay > http://blogrium.com/ > _______________________________________________ > engine-developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > -- * J * ~ _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
