I''ve developed a very useful (at least to me) plugin for rails. How do I go about releasing it. I have an account with rubyforge but I don''t know how to let rails know about it. Charlie Bowman www.recentrambles.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/e8d3909e/attachment.html
You can post it at the wiki and/or at my new plugin directory: http:// www.agilewebdevelopment.com/plugins :) On Apr 18, 2006, at 8:13 AM, Charlie Bowman wrote:> I''ve developed a very useful (at least to me) plugin for rails. > How do I go about releasing it. I have an account with rubyforge > but I don''t know how to let rails know about it. > > Charlie Bowman > www.recentrambles.com > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/ab64679f/attachment.html
Charlie Bowman wrote:> I''ve developed a very useful (at least to me) plugin for rails. How do > I go about releasing it. I have an account with rubyforge but I don''t > know how to let rails know about it. > > Charlie Bowman > www.recentrambles.comCharlie, I don''t know how helpful this will be but the Rails Recipes book tells you how to do that. BTW, what does your plugin do? - Rob D. -- Posted via http://www.ruby-forum.com/.
It''s cool that the recipes books details the process, but you would
think that this would be posted in big bold letters somewhere since it
is for the good of the community. My plugin adds a page expiration
method to expire all pages cached under an action or controller. Here
are two examples and thier results.
expire_each_page(:controller => ''blog'', :action
=> ''view'')
This will expire all pages recursively under public/blog/view. (ie
public/blog/view.html and publice/blog/view/2/old/4.html)
expire_each_page(:controller => ''blog'')
This will expire all pages recursively under public/blog/ (ie
public/blog.html and publice/blog/view/2/old/4.html)
So let me get this straight. All I need to release a plugin is an svn
repository. I then just add the link to the wiki and
http://www.agilewebdevelopment.com/plugins
If I do the above rails will automatically find the plugin?
On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote:
> Charlie Bowman wrote:
> > I''ve developed a very useful (at least to me) plugin for
rails. How do
> > I go about releasing it. I have an account with rubyforge but I
don''t
> > know how to let rails know about it.
> >
> > Charlie Bowman
> > www.recentrambles.com
>
> Charlie,
>
> I don''t know how helpful this will be but the Rails Recipes book
tells
> you how to do that. BTW, what does your plugin do?
>
> - Rob D.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/3d4df225/attachment.html
You need to add it to the wiki for the plugin script to know about it. I''m working on getting the script to know about my new site, but that''s not in place yet. On Apr 18, 2006, at 9:27 AM, Charlie Bowman wrote:> It''s cool that the recipes books details the process, but you would > think that this would be posted in big bold letters somewhere since > it is for the good of the community. My plugin adds a page > expiration method to expire all pages cached under an action or > controller. Here are two examples and thier results. > > expire_each_page(:controller => ''blog'', :action => ''view'') > This will expire all pages recursively under public/blog/view. > (ie public/blog/view.html and publice/blog/view/2/old/4.html) > expire_each_page(:controller => ''blog'') > This will expire all pages recursively under public/blog/ (ie > public/blog.html and publice/blog/view/2/old/4.html) > > So let me get this straight. All I need to release a plugin is an > svn repository. I then just add the link to the wiki and http:// > www.agilewebdevelopment.com/plugins > If I do the above rails will automatically find the plugin? > > On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote: >> Charlie Bowman wrote: >> > I''ve developed a very useful (at least to me) plugin for rails. >> How do >> > I go about releasing it. I have an account with rubyforge but I >> don''t >> > know how to let rails know about it. >> > >> > Charlie Bowman >> > www.recentrambles.com >> >> Charlie, >> >> I don''t know how helpful this will be but the Rails Recipes book >> tells >> you how to do that. BTW, what does your plugin do? >> >> - Rob D. >> > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/8f23f562/attachment.html
It sure would be nice if there was a database of the plugins. Screen scraping a wiki seems like a terrible way to handle such a major feature of rails. How are you trying to handle it on your site? On Tue, 2006-04-18 at 09:54 -0700, Benjamin Curtis wrote:> You need to add it to the wiki for the plugin script to know about it. > I''m working on getting the script to know about my new site, but > that''s not in place yet. > > > > On Apr 18, 2006, at 9:27 AM, Charlie Bowman wrote: > > > > > It''s cool that the recipes books details the process, but you would > > think that this would be posted in big bold letters somewhere since > > it is for the good of the community. My plugin adds a page > > expiration method to expire all pages cached under an action or > > controller. Here are two examples and thier results. > > > > expire_each_page(:controller => ''blog'', :action => > > ''view'') > > This will expire all pages recursively under public/blog/view. > > (ie public/blog/view.html and publice/blog/view/2/old/4.html) > > expire_each_page(:controller => ''blog'') > > This will expire all pages recursively under public/blog/ (ie > > public/blog.html and publice/blog/view/2/old/4.html) > > > > So let me get this straight. All I need to release a plugin is an > > svn repository. I then just add the link to the wiki and > > http://www.agilewebdevelopment.com/plugins > > If I do the above rails will automatically find the plugin? > > > > On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote: > > > > > Charlie Bowman wrote: > > > > I''ve developed a very useful (at least to me) plugin for rails. How do > > > > I go about releasing it. I have an account with rubyforge but I don''t > > > > know how to let rails know about it. > > > > > > > > Charlie Bowman > > > > www.recentrambles.com > > > > > > Charlie, > > > > > > I don''t know how helpful this will be but the Rails Recipes book tells > > > you how to do that. BTW, what does your plugin do? > > > > > > - Rob D. > > > > > > > > > > > > > _______________________________________________ > > Rails mailing list > > Rails@lists.rubyonrails.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/c0998973/attachment.html
Yup, my goal is to make that database. The first step is to get the content over from the wiki, then get the plugin installer script to know about my database, link people from the wiki to the new site, and finally end up with a better resource for the plugins than an easily-spammable wiki page. My site is open for adding and editing (everyone please feel free to add to the content from the content in the wiki!) and I''ll play the part of editor to make sure the information is good. I''m also very interested in any ideas people have for making it a better resource. As you say, plugins are a major feature of rails, and it''s time we have a great database for them. On Apr 18, 2006, at 10:03 AM, Charlie Bowman wrote:> It sure would be nice if there was a database of the plugins. > Screen scraping a wiki seems like a terrible way to handle such a > major feature of rails. How are you trying to handle it on your site? > > On Tue, 2006-04-18 at 09:54 -0700, Benjamin Curtis wrote: >> You need to add it to the wiki for the plugin script to know about >> it. I''m working on getting the script to know about my new site, >> but that''s not in place yet. >> >> On Apr 18, 2006, at 9:27 AM, Charlie Bowman wrote: >> >>> It''s cool that the recipes books details the process, but you >>> would think that this would be posted in big bold letters >>> somewhere since it is for the good of the community. My plugin >>> adds a page expiration method to expire all pages cached under an >>> action or controller. Here are two examples and thier results. >>> >>> expire_each_page(:controller => ''blog'', :action => >>> ''view'') >>> This will expire all pages recursively under public/blog/ >>> view. (ie public/blog/view.html and publice/blog/view/2/old/4.html) >>> expire_each_page(:controller => ''blog'') >>> This will expire all pages recursively under public/blog/ (ie >>> public/blog.html and publice/blog/view/2/old/4.html) >>> >>> So let me get this straight. All I need to release a plugin is >>> an svn repository. I then just add the link to the wiki and >>> http://www.agilewebdevelopment.com/plugins >>> If I do the above rails will automatically find the plugin? >>> >>> On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote: >>>> Charlie Bowman wrote: >>>> > I''ve developed a very useful (at least to me) plugin for >>>> rails. How do >>>> > I go about releasing it. I have an account with rubyforge but >>>> I don''t >>>> > know how to let rails know about it. >>>> > >>>> > Charlie Bowman >>>> > www.recentrambles.com >>>> >>>> Charlie, >>>> >>>> I don''t know how helpful this will be but the Rails Recipes book >>>> tells >>>> you how to do that. BTW, what does your plugin do? >>>> >>>> - Rob D. >>>> >>> >>> >>> _______________________________________________ >>> Rails mailing list >>> Rails@lists.rubyonrails.org >>> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> >> _______________________________________________ >> Rails mailing list >> Rails@lists.rubyonrails.org >> http://lists.rubyonrails.org/mailman/listinfo/rails > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/bc58f283/attachment.html
Hi Benjamin, A couple of weeks back I started in on a similar project but got sidetracked - very glad to see someone is taking this on. My primary driver for having a better resource than the wiki was for me as a plugin author to be able to communicate with people who are using my plugins. A dedicated mailing list is too heavy (imho) if all you want to say is "hey, I just fixed a bug" and I''m reluctant to spam the rails list every time I have news about something only a small fraction of people are interested in (it''s not so much that it''s rude, it''s more that the messages are likely to be lost in the sheer volume of the rails list). So, what be cool is: a) allow plugin authors to have accounts on your site so that they can self-manage the data (such as homepage, latest version. svn url etc). b) allow plugin authors to add news snippets - just a few hundred characters of text with an optional URL field that could point to a blog entry (or somesuch) that explains the news in greater depth. c) allow people to subscribe to RSS feeds on your site to pull in news for a given plugin (it would be *very* cool if the feed URL could allow you to pull in news for multiple plugins of your choosing) and finally: d) a plugin which users could install that (in development mode) displayed the plugin data (homepage etc) for each installed plugin in their project as well as a link to look at the latest news for the plugin (or even the text of the news itself). It could slurp the RSS feed from your site and present it in pretty html. Anyhow, that''s the sort of thing that would make *me* happy, dunno if anyone else wants it tho. If you think that those are good features but you don''t have the time to implement them then feel free to ping me off the list and I''ll see if I can scrape together some time to lend a hand. Regards, Trevor -- Trevor Squires http://somethinglearned.com On 18-Apr-06, at 10:11 AM, Benjamin Curtis wrote:> Yup, my goal is to make that database. The first step is to get > the content over from the wiki, then get the plugin installer > script to know about my database, link people from the wiki to the > new site, and finally end up with a better resource for the plugins > than an easily-spammable wiki page. > > My site is open for adding and editing (everyone please feel free > to add to the content from the content in the wiki!) and I''ll play > the part of editor to make sure the information is good. I''m also > very interested in any ideas people have for making it a better > resource. > > As you say, plugins are a major feature of rails, and it''s time we > have a great database for them. > > On Apr 18, 2006, at 10:03 AM, Charlie Bowman wrote: > >> It sure would be nice if there was a database of the plugins. >> Screen scraping a wiki seems like a terrible way to handle such a >> major feature of rails. How are you trying to handle it on your >> site? >> >> On Tue, 2006-04-18 at 09:54 -0700, Benjamin Curtis wrote: >>> You need to add it to the wiki for the plugin script to know >>> about it. I''m working on getting the script to know about my new >>> site, but that''s not in place yet. >>> >>> On Apr 18, 2006, at 9:27 AM, Charlie Bowman wrote: >>> >>>> It''s cool that the recipes books details the process, but you >>>> would think that this would be posted in big bold letters >>>> somewhere since it is for the good of the community. My plugin >>>> adds a page expiration method to expire all pages cached under >>>> an action or controller. Here are two examples and thier results. >>>> >>>> expire_each_page(:controller => ''blog'', :action => >>>> ''view'') >>>> This will expire all pages recursively under public/blog/ >>>> view. (ie public/blog/view.html and publice/blog/view/2/old/4.html) >>>> expire_each_page(:controller => ''blog'') >>>> This will expire all pages recursively under public/blog/ >>>> (ie public/blog.html and publice/blog/view/2/old/4.html) >>>> >>>> So let me get this straight. All I need to release a plugin is >>>> an svn repository. I then just add the link to the wiki and >>>> http://www.agilewebdevelopment.com/plugins >>>> If I do the above rails will automatically find the plugin? >>>> >>>> On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote: >>>>> Charlie Bowman wrote: >>>>> > I''ve developed a very useful (at least to me) plugin for >>>>> rails. How do >>>>> > I go about releasing it. I have an account with rubyforge >>>>> but I don''t >>>>> > know how to let rails know about it. >>>>> > >>>>> > Charlie Bowman >>>>> > www.recentrambles.com >>>>> >>>>> Charlie, >>>>> >>>>> I don''t know how helpful this will be but the Rails Recipes >>>>> book tells >>>>> you how to do that. BTW, what does your plugin do? >>>>> >>>>> - Rob D. >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Rails mailing list >>>> Rails@lists.rubyonrails.org >>>> http://lists.rubyonrails.org/mailman/listinfo/rails >>> >>> >>> _______________________________________________ >>> Rails mailing list >>> Rails@lists.rubyonrails.org >>> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> _______________________________________________ >> Rails mailing list >> Rails@lists.rubyonrails.org >> http://lists.rubyonrails.org/mailman/listinfo/rails > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/0305fb42/attachment-0001.html
Thanks for the comments! These are excellent ideas and would make great additions to the site. I''ll mull ''em over a bit and see what I can crank out myself vs. where I would need some help. I was thinking of having a checkout of each plugin repository, updating them on a regular basis, and publishing some sort of delta via RSS. Having the plugin author come by and do that (with better info, no doubt), like RAA does it, is a much better idea. :) On Apr 18, 2006, at 10:56 AM, Trevor Squires wrote:> Hi Benjamin, > > A couple of weeks back I started in on a similar project but got > sidetracked - very glad to see someone is taking this on. > > My primary driver for having a better resource than the wiki was > for me as a plugin author to be able to communicate with people who > are using my plugins. > > A dedicated mailing list is too heavy (imho) if all you want to say > is "hey, I just fixed a bug" and I''m reluctant to spam the rails > list every time I have news about something only a small fraction > of people are interested in (it''s not so much that it''s rude, it''s > more that the messages are likely to be lost in the sheer volume of > the rails list). > > So, what be cool is: > > a) allow plugin authors to have accounts on your site so that they > can self-manage the data (such as homepage, latest version. svn url > etc). > b) allow plugin authors to add news snippets - just a few hundred > characters of text with an optional URL field that could point to a > blog entry (or somesuch) that explains the news in greater depth. > c) allow people to subscribe to RSS feeds on your site to pull in > news for a given plugin (it would be *very* cool if the feed URL > could allow you to pull in news for multiple plugins of your choosing) > > and finally: > > d) a plugin which users could install that (in development mode) > displayed the plugin data (homepage etc) for each installed plugin > in their project as well as a link to look at the latest news for > the plugin (or even the text of the news itself). It could slurp > the RSS feed from your site and present it in pretty html. > > Anyhow, that''s the sort of thing that would make *me* happy, dunno > if anyone else wants it tho. > > If you think that those are good features but you don''t have the > time to implement them then feel free to ping me off the list and > I''ll see if I can scrape together some time to lend a hand. > > Regards, > Trevor > -- > Trevor Squires > http://somethinglearned.com > > > On 18-Apr-06, at 10:11 AM, Benjamin Curtis wrote: > >> Yup, my goal is to make that database. The first step is to get >> the content over from the wiki, then get the plugin installer >> script to know about my database, link people from the wiki to the >> new site, and finally end up with a better resource for the >> plugins than an easily-spammable wiki page. >> >> My site is open for adding and editing (everyone please feel free >> to add to the content from the content in the wiki!) and I''ll play >> the part of editor to make sure the information is good. I''m also >> very interested in any ideas people have for making it a better >> resource. >> >> As you say, plugins are a major feature of rails, and it''s time we >> have a great database for them. >> >> On Apr 18, 2006, at 10:03 AM, Charlie Bowman wrote: >> >>> It sure would be nice if there was a database of the plugins. >>> Screen scraping a wiki seems like a terrible way to handle such a >>> major feature of rails. How are you trying to handle it on your >>> site? >>> >>> On Tue, 2006-04-18 at 09:54 -0700, Benjamin Curtis wrote: >>>> You need to add it to the wiki for the plugin script to know >>>> about it. I''m working on getting the script to know about my >>>> new site, but that''s not in place yet. >>>> >>>> On Apr 18, 2006, at 9:27 AM, Charlie Bowman wrote: >>>> >>>>> It''s cool that the recipes books details the process, but you >>>>> would think that this would be posted in big bold letters >>>>> somewhere since it is for the good of the community. My plugin >>>>> adds a page expiration method to expire all pages cached under >>>>> an action or controller. Here are two examples and thier results. >>>>> >>>>> expire_each_page(:controller => ''blog'', :action => >>>>> ''view'') >>>>> This will expire all pages recursively under public/blog/ >>>>> view. (ie public/blog/view.html and publice/blog/view/2/old/ >>>>> 4.html) >>>>> expire_each_page(:controller => ''blog'') >>>>> This will expire all pages recursively under public/blog/ >>>>> (ie public/blog.html and publice/blog/view/2/old/4.html) >>>>> >>>>> So let me get this straight. All I need to release a plugin is >>>>> an svn repository. I then just add the link to the wiki and >>>>> http://www.agilewebdevelopment.com/plugins >>>>> If I do the above rails will automatically find the plugin? >>>>> >>>>> On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote: >>>>>> Charlie Bowman wrote: >>>>>> > I''ve developed a very useful (at least to me) plugin for >>>>>> rails. How do >>>>>> > I go about releasing it. I have an account with rubyforge >>>>>> but I don''t >>>>>> > know how to let rails know about it. >>>>>> > >>>>>> > Charlie Bowman >>>>>> > www.recentrambles.com >>>>>> >>>>>> Charlie, >>>>>> >>>>>> I don''t know how helpful this will be but the Rails Recipes >>>>>> book tells >>>>>> you how to do that. BTW, what does your plugin do? >>>>>> >>>>>> - Rob D. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Rails mailing list >>>>> Rails@lists.rubyonrails.org >>>>> http://lists.rubyonrails.org/mailman/listinfo/rails >>>> >>>> >>>> _______________________________________________ >>>> Rails mailing list >>>> Rails@lists.rubyonrails.org >>>> http://lists.rubyonrails.org/mailman/listinfo/rails >>> >>> _______________________________________________ >>> Rails mailing list >>> Rails@lists.rubyonrails.org >>> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> _______________________________________________ >> Rails mailing list >> Rails@lists.rubyonrails.org >> http://lists.rubyonrails.org/mailman/listinfo/rails > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/d73a80e3/attachment-0001.html
I like the idea of letting the plugin author have control of the documentation on the site. It would make it a little more like CPAN, which is always a great thing! On Tue, 2006-04-18 at 11:15 -0700, Benjamin Curtis wrote:> Thanks for the comments! These are excellent ideas and would make > great additions to the site. I''ll mull ''em over a bit and see what I > can crank out myself vs. where I would need some help. > > > > I was thinking of having a checkout of each plugin repository, > updating them on a regular basis, and publishing some sort of delta > via RSS. Having the plugin author come by and do that (with better > info, no doubt), like RAA does it, is a much better idea. :) > > > On Apr 18, 2006, at 10:56 AM, Trevor Squires wrote: > > > > > Hi Benjamin, > > > > > > > > A couple of weeks back I started in on a similar project but got > > sidetracked - very glad to see someone is taking this on. > > > > > > My primary driver for having a better resource than the wiki was for > > me as a plugin author to be able to communicate with people who are > > using my plugins. > > > > > > A dedicated mailing list is too heavy (imho) if all you want to say > > is "hey, I just fixed a bug" and I''m reluctant to spam the rails > > list every time I have news about something only a small fraction of > > people are interested in (it''s not so much that it''s rude, it''s more > > that the messages are likely to be lost in the sheer volume of the > > rails list). > > > > > > So, what be cool is: > > > > > > a) allow plugin authors to have accounts on your site so that they > > can self-manage the data (such as homepage, latest version. svn url > > etc). > > b) allow plugin authors to add news snippets - just a few hundred > > characters of text with an optional URL field that could point to a > > blog entry (or somesuch) that explains the news in greater depth. > > c) allow people to subscribe to RSS feeds on your site to pull in > > news for a given plugin (it would be *very* cool if the feed URL > > could allow you to pull in news for multiple plugins of your > > choosing) > > > > > > and finally: > > > > > > d) a plugin which users could install that (in development mode) > > displayed the plugin data (homepage etc) for each installed plugin > > in their project as well as a link to look at the latest news for > > the plugin (or even the text of the news itself). It could slurp > > the RSS feed from your site and present it in pretty html. > > > > > > Anyhow, that''s the sort of thing that would make *me* happy, dunno > > if anyone else wants it tho. > > > > > > If you think that those are good features but you don''t have the > > time to implement them then feel free to ping me off the list and > > I''ll see if I can scrape together some time to lend a hand. > > > > > > Regards, > > Trevor > > -- > > Trevor Squires > > http://somethinglearned.com > > > > > > > > > > > > > > On 18-Apr-06, at 10:11 AM, Benjamin Curtis wrote: > > > > > > > > > Yup, my goal is to make that database. The first step is to get > > > the content over from the wiki, then get the plugin installer > > > script to know about my database, link people from the wiki to the > > > new site, and finally end up with a better resource for the > > > plugins than an easily-spammable wiki page. > > > > > > > > > > > > My site is open for adding and editing (everyone please feel free > > > to add to the content from the content in the wiki!) and I''ll play > > > the part of editor to make sure the information is good. I''m also > > > very interested in any ideas people have for making it a better > > > resource. > > > > > > > > > As you say, plugins are a major feature of rails, and it''s time we > > > have a great database for them. > > > > > > > > > On Apr 18, 2006, at 10:03 AM, Charlie Bowman wrote: > > > > > > > > > > > > > It sure would be nice if there was a database of the plugins. > > > > Screen scraping a wiki seems like a terrible way to handle such > > > > a major feature of rails. How are you trying to handle it on > > > > your site? > > > > > > > > On Tue, 2006-04-18 at 09:54 -0700, Benjamin Curtis wrote: > > > > > > > > > You need to add it to the wiki for the plugin script to know > > > > > about it. I''m working on getting the script to know about my > > > > > new site, but that''s not in place yet. > > > > > > > > > > On Apr 18, 2006, at 9:27 AM, Charlie Bowman wrote: > > > > > > > > > > > > > > > > It''s cool that the recipes books details the process, but > > > > > > you would think that this would be posted in big bold > > > > > > letters somewhere since it is for the good of the community. > > > > > > My plugin adds a page expiration method to expire all pages > > > > > > cached under an action or controller. Here are two examples > > > > > > and thier results. > > > > > > > > > > > > expire_each_page(:controller => ''blog'', :action => > > > > > > ''view'') > > > > > > This will expire all pages recursively under > > > > > > public/blog/view. (ie public/blog/view.html and > > > > > > publice/blog/view/2/old/4.html) > > > > > > expire_each_page(:controller => ''blog'') > > > > > > This will expire all pages recursively under > > > > > > public/blog/ (ie public/blog.html and > > > > > > publice/blog/view/2/old/4.html) > > > > > > > > > > > > So let me get this straight. All I need to release a plugin > > > > > > is an svn repository. I then just add the link to the wiki > > > > > > and http://www.agilewebdevelopment.com/plugins > > > > > > If I do the above rails will automatically find the plugin? > > > > > > > > > > > > On Tue, 2006-04-18 at 18:04 +0200, Robert Dempsey wrote: > > > > > > > > > > > > > Charlie Bowman wrote: > > > > > > > > I''ve developed a very useful (at least to me) plugin for rails. How do > > > > > > > > I go about releasing it. I have an account with rubyforge but I don''t > > > > > > > > know how to let rails know about it. > > > > > > > > > > > > > > > > Charlie Bowman > > > > > > > > www.recentrambles.com > > > > > > > > > > > > > > Charlie, > > > > > > > > > > > > > > I don''t know how helpful this will be but the Rails Recipes book tells > > > > > > > you how to do that. BTW, what does your plugin do? > > > > > > > > > > > > > > - Rob D. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Rails mailing list > > > > > > Rails@lists.rubyonrails.org > > > > > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Rails mailing list > > > > > Rails@lists.rubyonrails.org > > > > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Rails mailing list > > > > Rails@lists.rubyonrails.org > > > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > > > > > > _______________________________________________ > > > Rails mailing list > > > Rails@lists.rubyonrails.org > > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > > _______________________________________________ > > Rails mailing list > > Rails@lists.rubyonrails.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060418/9da5d3e7/attachment.html
I''m preparing my plugin for release and noticed the script/plugin scraper requires your plugin svn repository to adopt an undocumented naming scheme AFAIK. Your repository path must have "/plugins/" and can''t have "/browser/" in the string. Also rubyforge svn links have some issue I haven''t tracked down yet. In any case, there''s more than just adding your plugin to the wiki and agilewebdevelopment.com if you want your plugin to be qualified for RailsDay. I''m just going to put SVN on a textdrive account.. -Bill On 4/18/06, Charlie Bowman <charlie@castlebranch.com> wrote:> > I like the idea of letting the plugin author have control of the > documentation on the site. It would make it a little more like CPAN, which > is always a great thing! > > > On Tue, 2006-04-18 at 11:15 -0700, Benjamin Curtis wrote: > > Thanks for the comments! These are excellent ideas and would make great > additions to the site. I''ll mull ''em over a bit and see what I can crank > out myself vs. where I would need some help. > > > > I was thinking of having a checkout of each plugin repository, updating > them on a regular basis, and publishing some sort of delta via RSS. Having > the plugin author come by and do that (with better info, no doubt), like RAA > does it, is a much better idea. :) > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060609/1d022ddf/attachment.html
Benjamin Curtis wrote:> You can post it at the wiki and/or at my new plugin directory: http:// > www.agilewebdevelopment.com/plugins > > :)Great to see a repository for plugins coming along. Very needed! Perhaps you would want to coordinate efforts with the RadRails team as they''re doing the same here: http://plugins.radrails.org/ -- Posted via http://www.ruby-forum.com/.