jeffl
April 4, 2006, 1:38pm
1
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.
–
Jeff L.
http://blogrium.com/
jeffl
April 4, 2006, 3:01pm
2
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?
On 4/4/06, Jeff L. [email protected] wrote:
‘http://svn.rails-engines.org/plugins/engines ’]
into a new app with:
engine-developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
–
jeffl
April 4, 2006, 3:05pm
3
Oooo, great idea. I’m on it.
-jeff
On 4/4/06, James A. [email protected] wrote:
engines (or well, any kind of plugin)…
Commands::Plugin.parse! [‘install’, ‘http://my-cool-engine ’]
$ script/plugin install http://example.com/svn/my_installer
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
–
Jeff L.
http://blogrium.com/
jeffl
April 4, 2006, 3:29pm
4
Done. http://dev.rails-engines.org/tickets/122
On 4/4/06, Jeff L. [email protected] wrote:
require ‘commands/plugin’
Commands::Plugin.parse! [‘remove’, ‘my_installer’]
Jeff L.
~
–
Jeff L.
http://blogrium.com/
jeffl
April 4, 2006, 4:28pm
5
You know, we could even push Engines.start :whatever into the
environment file here.
I’m doing that in my engines, but I don’t know if it’s something we’d
want as default engine behavior…
-jeff
On 4/4/06, James A. [email protected] wrote:
-jeff
On 4/4/06, Jeff L. [email protected] wrote:
‘http://svn.rails-engines.org/plugins/engines ’]
into a new app with:
engine-developers mailing list
[email protected]
–
engine-developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
–
Jeff L.
http://blogrium.com/
jeffl
April 4, 2006, 4:37pm
6
By ‘push’ I presume you mean write (append) it to the file? I guess it
could be done… Probably the best thing for the moment my be sticking
that information (what you’re doing at the moment) up on the wiki.
On 4/4/06, Jeff L. [email protected] wrote:
On 4/4/06, James A. [email protected] wrote:
engines (or well, any kind of plugin)…
Commands::Plugin.parse! [‘install’, ‘http://my-cool-engine ’]
$ script/plugin install http://example.com/svn/my_installer
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
http://blogrium.com/
engine-developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
–
jeffl
April 4, 2006, 3:32pm
7
Thanks
On 4/4/06, Jeff L. [email protected] wrote:
It would certainly be good if when you tried to install an engine, it
process. You can make a new plugin with just this file, called
Commands::Plugin.parse! [‘install’,
if this is already a well known practice or something.
–
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
–
jeffl
April 4, 2006, 4:52pm
8