jeffkreeftmeijer / navvy
- Source
- Commits
- Network (16)
- Issues (1)
- Downloads (10)
- Wiki (13)
- Graphs
-
Branch:
develop
| name | age | message | |
|---|---|---|---|
| |
.document | Tue Jan 05 03:25:38 -0800 2010 | |
| |
.gitignore | Sun May 23 15:04:20 -0700 2010 | |
| |
Gemfile | Thu Aug 12 13:20:19 -0700 2010 | |
| |
Gemfile.lock | Thu Aug 12 16:26:08 -0700 2010 | |
| |
LICENSE | Tue Jan 05 03:25:38 -0800 2010 | |
| |
README.textile | Sun Jun 27 11:59:43 -0700 2010 | |
| |
Rakefile | Mon May 24 02:16:33 -0700 2010 | |
| |
generators/ | Sun Jun 27 05:23:06 -0700 2010 | |
| |
lib/ | Thu Aug 12 16:26:08 -0700 2010 | |
| |
navvy.gemspec | Thu Aug 12 11:44:34 -0700 2010 | |
| |
spec/ | Thu Aug 12 13:20:19 -0700 2010 |
Navvy
Navvy is a simple Ruby background job processor inspired by delayed_job, but aiming for database agnosticism. Currently Navvy supports ActiveRecord, MongoMapper, Sequel, DataMapper and Mongoid but it’s extremely easy to write an adapter for your favorite ORM.
Navvy doesn’t depend on Rails, it’s a pure Ruby library. There are generators for Rails 2 and Rails 3, though.
“Navvy is a shorter form of navigator (UK) or navigational engineer (USA) and is particularly applied to describe the manual labourers working on major civil engineering projects. The term was coined in the late 18th century in Britain when numerous canals were being built, which were also sometimes known as “navigations”. Canal navvies typically worked with shovels, pickaxes and barrows.” – Wikipedia
Using Navvy
Check out the Installation Guide and the Getting Started Guide to get up and running. If you have any questions or problems, don’t hesitate to ask.
Contributing
Found an issue? Have a great idea? Want to help? Great! Create an issue issue for it, ask, or even better; fork the project and fix the problem yourself. Pull requests are always welcome. :)
License
Copyright © 2009 Jeff Kreeftmeijer, released under the MIT license
