ActiveRecord migrations without Rails

Submitted by Christoph Olszowka 2011-03-05 10:01:23 UTC
Source:  http://exposinggotchas.blogspot.com/2011/02/activerecord-migrations-without-rails.html

Referenced projects

Rake

Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax. Rake has the following features: * Rakefiles (rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax to worry about (is that a tab or a space?) * Users can specify tasks with prerequisites. * Rake supports rule patterns to synthesize implicit tasks. * Flexible FileLists that act like arrays but know about manipulating file names and paths. * A library of prepackaged tasks to make building rakefiles easier. For example, tasks for building tarballs and publishing to FTP or SSH sites. (Formerly tasks for building RDoc and Gems were included in rake but they're now available in RDoc and RubyGems respectively.) * Supports parallel execution of tasks.

Rubygem rake

Total Downloads
46371855
Releases
59
Current Version
10.3.0
Released
2014-04-15 00:00:00 UTC
First Release
2004-09-15 04:00:00 UTC
Depends on following gems
Depending Gems
17311

Github jimweirich/rake

Watchers
975
Forks
242
Development activity
Active
Last commit
2014-04-17 23:26:45 UTC
Contributors
30
Issues
Wiki pages

Active Record

Databases on Rails. Build a persistent domain model by mapping database tables to Ruby classes. Strong conventions for associations, validations, aggregations, migrations, and testing come baked-in.

Rubygem activerecord

Total Downloads
31271101
Releases
187
Current Version
4.1.0
Released
2014-04-08 00:00:00 UTC
First Release
2004-10-25 04:00:00 UTC

Github rails/rails

Watchers
20812
Forks
7365
Development activity
Very active
Last commit
2014-02-16 18:01:09 UTC
Contributors
2188
Issues
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.