Changesets can be listed by changeset number.
The Git repository is here.
Revision log for rool/rails/hub/trunk/VERSION
| Date | Changeset | Author | Log |
|---|---|---|---|
| 04/16/2016 10:21 | 470 | rool | Version 1.0.2 with updated reCaptcha |
| 08/26/2012 17:36 | 427 | rool | Version 1.0.1 of the Hub application, which adds reCaptcha verification to the sign-up form. Implemented after spambots attacked the ROOL site and signed up hundreds of bogus users. |
| 08/26/2012 17:35 | 341 | rool | Lots of changes to Hub to make it Rails 2.3.11 compatible. This is being checked in as one large changeset because it doesn't really split down into smaller components without having something that doesn't function in the intermediate steps. |
| 08/26/2012 17:35 | 263 | rool | Update Hub application and library gem VERSION files following Changeset #261 and Changeset #262. Note that this version of the application requires the corresponding version of the gem (0.2.6). |
| 08/26/2012 17:34 | 181 | rool | Updated to work with Rails 1.2. Small bug fix in the account controller (missing quotes around name of the Tasks controller in a method call). |
| 08/26/2012 17:34 | 166 | rool | Added pagination to Hub account lists. Sort order is whatever the database feels like (so, usually, least to most recently updated). User-selectable sorting might be needed in future but this current implementation does, at least, provide the feature requested in Ticket #99. Rather than using the much-maligned Rails default paginator, an external paginator gem is used - "gem install paginator" grabs it. For more, see: http://codefluency.com/2006/10/24/paginator-released http://paginator.rubyforge.org/ |
| 08/26/2012 17:34 | 112 | adh | After many attempts, a new version of Hub that requires the HubSsoLib Gem v0.1.0 (see future Changeset #113). HubSsoLib no longer uses cookies because of problems with the Rails cookies interface and the only viable workaround being scuppered by after_filter code not always being called (e.g. if you redirect from within a before_filter). Ultimately, the solution of using a (very) simple DRb-based authorisation server, as suggested by RubyPanther on the rubyonrails IRC channel, is perhaps a little slower but a lot more scalable and a lot more reliable. The server is included in the 'server' directory. |
