#### MultiRails by Relevance, http://thinkrelevance.com Rob Sanheim - MultiRails lead MultiRails lets you test your Rails plugin or app against many versions of Rails in one sweep. #### DESCRIPTION: MultiRails allows easy testing against multiple versions of Rails for your Rails specific gem or plugin. It also has tentative support testing Rails applications against multiple versions of Rails. Use MultiRails to hook in Rails 2.0 testing in your continuous integration. Still working on Rails 2.0 support? Use MultiRails to see where your test suite falls down against the 2.0 preview releases of Rails. MultiRails was initially developed by members of Relevance while developing Streamlined against edge Rails. To see how Streamlined uses MultiRails, go to http://trac.streamlinedframework.org. #### FEATURES: * easily test plugins/extensions using a require from your test_helper.rb and a require in your RakeFile * rake tasks to test against a specified version of Rails, the latest version, or all versions * tentative support for testing plain Rails apps against multiple versions of Rails * Uses rubygems for version management of Rails #### TODOs: * improve docs on how to override what files are required by multi_rails * maybe add ability to load plain Rails versions -- ie checked out copies not in RubyGems #### NOTES: * (__For Rails apps only__) multi_rails will rename your vendor/rails directory to vendor/rails.off if it finds one within your rails app. We have to do this to make Rails fall back to RubyGems rails. Multi_rails will rename back to the correct vendor/rails when done testing, so it will not interrupt your app in normal use. * (__For Rails apps only__) multi_rails needs to add a line to top of your environment.rb to hook into -- see the instructions below for more details

MultiRails was initially developed by members of Relevance while developing Streamlined against edge Rails. To see how Streamlined uses MultiRails, go to http://streamlinedframework.org. == FEATURES/PROBLEMS: * easily test plugins/extensions to Rails using a one line require from your test_helper.rb * rake tasks to test against a specific version of Rails, or all versions of Rails available locally as Gems == TODOs:

A simple pagination plugin for DataMapper

A simple wrapper for dbi that provides two simple functions dbconnect(profile) and query(sql), along with auth profiles via a configuration file.

This is a small wrapper around HIDAPI. I couldn't get other HIDAPI wrappers to work, so I wrote this one. I'm using it to communicate with my keyboard, so it really only supports enough of the HIDAPI to do that.

Adds migration helpers to allow for postgres-specific stuff like real constraints

* my project demo

== FEATURES/PROBLEMS: Sometimes it can be slow == SYNOPSIS: Credentials credentials = { :username => 'email@address.com', :password => 'SuperSecretPassword' }

MySpaceID lets your users log on using their MySpace account info, after which their MySpaceID data becomes available; that is, your web servers will be able to communicate with our web servers and request user data. This SDK project contains examples of the base API code necessary to make signed requests against the MySpaceID REST API. To use the MySpaceID API, you first need to register on the MySpace Developer Site, create an app, and obtain a consumer key and secret. Information about these procedures, and about MySpaceID in general, is available at the MySpaceID Developer Wiki: http://wiki.developer.myspace.com/index.php?title=Category:MySpaceID The MySpaceID Ruby SDK enables you to work with MySpace data using the OpenStack (OpenID, OAuth etc) and the MySpace REST APIs via easy-to-use high level interfaces. The best way to implement your own application is to take an existing sample and customize it. Working Examples in this SDK: * OAuth - make signed requests * OpenID + OAuth Hybrid - delegated login, and making signed requests Documentation * Ruby SDK Documentation Summary: samples/rails/README * Ruby SDK - API Documentation: http://myspaceid-ruby-sdk.googlecode.com/svn/trunk/doc/index.html

This extension to the MysqlAdapter in ActiveRecord enables bulk updates to schema definitions. Pr. default when calling connection#add_column the change will be executed a once, but Mysql allows for multiple changes to be executed in one SQL statement (http://dev.mysql.com/doc/refman/5.1/en/alter-table.html). The advantage of this is that it takes a lot less time, especially if the table is large.

Something summary

Updated for Ruby 2.X This is a packaged version of CSVScan, written by MoonWolf. If you can read Japanese, checkout README.ja for whatever he said. On a 10,000 line file: time cat example.csv | ruby fastercsv_benchmark.rb real 0m8.804s user 0m8.502s sys 0m0.304s time cat example.csv | ruby csvscan_benchmark.rb real 0m0.860s user 0m0.782s sys 0m0.088s

SEO friendly permalinks for your Active Record models

Batch edit passwords for domains managed at [http://access.enom.com](http://access.enom.com)

Provides the ActiveRecord helper method <tt>named_scope_for_time_attr</tt>. Given the name of a time attribute of an ActiveRecord model (e.g. <tt>created_at</tt> of <tt>Claim</tt>) it defines a correspondent named scope for easy access to an arbitrarily time range (scope).

namelib is a Ruby fork of NameCase, a library for converting denormalized names to be properly cased.

A simple API wrapper for Nanowrimo.org. Nanowrimo Word Count API documentation here: http://www.nanowrimo.org/eng/wordcount_api

youtube-g is a pure Ruby client for the YouTube GData API. It provides an easy way to access the latest YouTube video search results from your own programs. In comparison with the earlier Youtube search interfaces, this new API and library offers much-improved flexibility around executing complex search queries to obtain well-targeted video search results. More detail on the underlying source Google-provided API is available at: http://code.google.com/apis/youtube/overview.html

production_log_analyzer lets you find out which actions on a Rails site are slowing you down. Bug reports: http://rubyforge.org/tracker/?func=add&group_id=1513&atid=5921

== DESCRIPTION: Need makes ruby relative requires just work. Simply need a file with a relative path and the file will always be required correctly, regardless of what file your application is being launched through. Typically, ruby projects would unshift lib onto $PATH or use the File.dirname(__FILE__) trick. Using need means you don't have to worry about either of these. Assume you have two files, one directly in lib and the other in lib/extensions. Let's assume that file_a in lib requires file_b, in lib/extensions. Previously, you would doing some crazy load path unshifting or use the __FILE__ trick to make these requires flexible enough to work when your app is being accessed by rake, through a test suite, or required as a gem. Now, just use need. In file_a: need{"extensions/file_b"} need "extensions/file_b"