Project

navvy

0.09

Background Jobs

Repository is archived
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
navvyjeffkreeftmeijer/navvyHomepageDocumentationSource CodeBug TrackerWiki
Simple background job processor inspired by delayed_job, but aiming for database agnosticism.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
52,282
Stars
216
Forks
19
Watchers
4
 Releases
Current version
0.3.2
Total releases
13
First release
2010-01-10
Latest release
2011-01-01
 Issues
Open Issues
5
Closed Issues
4
Total Issues
9
Issue Closure Rate
44%
 Pull Requests
Open Pull Requests
2
Closed Pull Requests
2
Merged Pull Requests
2
Pull Request Acceptance Rate
33%
 Development
Primary Language
Ruby
Average date of last 50 commits
2010-10-18
Reverse Dependencies
1

 Dependencies

Development

bson_ext
>= 0
fuubar
~> 0.0
rake
>= 0
rspec
~> 2.0
sqlite3-ruby
>= 0
timecop
>= 0.3.5
yard
>= 0.5.2
 Project Readme

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. :)