I DuaneJohnson am currently updating the Plugins page. It’ll be more organized in just a bit. (January 12, 2006)
Plugins meta discussion:
To clean up this page, should we make individual pages for each plugin? Its going get long and messy sooner or later.
Yes. This page should have an overview, and a list of plugin’s and engines. —Larry Kelly
Are engines different enough from plugins to be listed separately?
If you want to package your own plugin, please do read Jamis Buck’s guide to plugins
Also check out this plugin manager which is now shipping with Rails 1.0 RC4 (0.14.3).
Are there any plans to have script/plugin support plugins which have repositories in a trunk/branches/tags structure?—JamesAdam
Yes. —RyanTomayko
Is there an answer to the error (after running ruby script/plugin) : No such file or directory script/plugin ?
Solution for missing script/plugin:
I struggled with this for a while before I discovered the ridiculously simple answer: It’s not enough to be using Rails 0.14 or later; you have to have generated your application from Rails 0.14 or later for script/plugin to be where it’s supposed to be.
cd to your Rails directory and type
rails your_application_name
Be careful! Rails will ask you whether you want to overwrite various files in your application- you’ll probably say no to most files in an existing application- and it will put the plugin script into place.
After you install the plugin using ruby script/plugin install url-of-plugin you’ll need to quit webrick using ctrl-c and restart it.
Probably obvious to all but us dummies.
On Windows, running script/plugin will result in “No such file or directory” errors unless you have installed the latest version of Subversion (Subversion homepage). I had not found this information anywhere else so I hope that it’s helpful. —DR
There needs to be some location where people can go to see which plugins are supported / tested for which version of rails. In some cases plugins will not work at all with 1.1, for example, and in other cases, there are specific versions of plugins that should be used with specific versions of Rails. The solution could be as simple as having plugin / generator / engine developers put this information in their plugin section here on the wiki. —KL
A TinderBox style system could be used to create a self updating chart of plugin <-> rails compatibility, though somebody would need to donate the hardware and net connection of course. It could be as simple as N rails installations on a single server (whichever versions are deemed useful to test) and each one automagically wiping clean, installing plugin X, running the tests, then moving on to the next plugin. —XE
By reading this plugin page I am still mystified. Is a plugin anything different than a subroutine library or a ruby module?
What is it’s intent, to add code to rails that your app can use? Or to modify existing rails functionality that my app is already using? Or what? I have no idea what sort of things should be built as plugins and what sort of things should not be built as plugins.
Is a plugin a way to install a new database interface? I would guess not but you can’t tell that from the plugin documentation.
Are the plugins in this wiki under the same licence as rails? Many seem to have no information about the author, copyrights or licence and this makes it harder to use them in a commercial application.
No. My plugins are all under the BSD license. The license is up to the plugin’s author.
Screencast on How to Develop Rails Plugins
http://www.rubyplus.org/episodes/10-How-to-develop-Plugins-in-Rails-The-Basics.html
I DuaneJohnson am currently updating the Plugins page. It’ll be more organized in just a bit. (January 12, 2006)
Plugins meta discussion:
To clean up this page, should we make individual pages for each plugin? Its going get long and messy sooner or later.
Yes. This page should have an overview, and a list of plugin’s and engines. —Larry Kelly
Are engines different enough from plugins to be listed separately?
If you want to package your own plugin, please do read Jamis Buck’s guide to plugins
Also check out this plugin manager which is now shipping with Rails 1.0 RC4 (0.14.3).
Are there any plans to have script/plugin support plugins which have repositories in a trunk/branches/tags structure?—JamesAdam
Yes. —RyanTomayko
Is there an answer to the error (after running ruby script/plugin) : No such file or directory script/plugin ?
Solution for missing script/plugin:
I struggled with this for a while before I discovered the ridiculously simple answer: It’s not enough to be using Rails 0.14 or later; you have to have generated your application from Rails 0.14 or later for script/plugin to be where it’s supposed to be.
cd to your Rails directory and type
rails your_application_name
Be careful! Rails will ask you whether you want to overwrite various files in your application- you’ll probably say no to most files in an existing application- and it will put the plugin script into place.
After you install the plugin using ruby script/plugin install url-of-plugin you’ll need to quit webrick using ctrl-c and restart it.
Probably obvious to all but us dummies.
On Windows, running script/plugin will result in “No such file or directory” errors unless you have installed the latest version of Subversion (Subversion homepage). I had not found this information anywhere else so I hope that it’s helpful. —DR
There needs to be some location where people can go to see which plugins are supported / tested for which version of rails. In some cases plugins will not work at all with 1.1, for example, and in other cases, there are specific versions of plugins that should be used with specific versions of Rails. The solution could be as simple as having plugin / generator / engine developers put this information in their plugin section here on the wiki. —KL
A TinderBox style system could be used to create a self updating chart of plugin <-> rails compatibility, though somebody would need to donate the hardware and net connection of course. It could be as simple as N rails installations on a single server (whichever versions are deemed useful to test) and each one automagically wiping clean, installing plugin X, running the tests, then moving on to the next plugin. —XE
By reading this plugin page I am still mystified. Is a plugin anything different than a subroutine library or a ruby module?
What is it’s intent, to add code to rails that your app can use? Or to modify existing rails functionality that my app is already using? Or what? I have no idea what sort of things should be built as plugins and what sort of things should not be built as plugins.
Is a plugin a way to install a new database interface? I would guess not but you can’t tell that from the plugin documentation.
Are the plugins in this wiki under the same licence as rails? Many seem to have no information about the author, copyrights or licence and this makes it harder to use them in a commercial application.
No. My plugins are all under the BSD license. The license is up to the plugin’s author.
Screencast on How to Develop Rails Plugins
http://www.rubyplus.org/episodes/10-How-to-develop-Plugins-in-Rails-The-Basics.html