jnunemaker / mongomapper
- Source
- Commits
- Network (158)
- Downloads (35)
- Wiki (4)
- Graphs
-
Branch:
master
A Ruby Object Mapper for Mongo
| name | age | message | |
|---|---|---|---|
 |
.gitignore | Sun Oct 18 17:07:48 -0700 2009 | |
| |
LICENSE | Fri May 22 16:20:23 -0700 2009 | |
| |
README.rdoc | Mon Feb 22 07:50:31 -0800 2010 | |
| |
Rakefile | Tue Mar 09 13:31:23 -0800 2010 | |
 |
bin/ | Sat Nov 14 20:18:45 -0800 2009 | |
| |
lib/ | Tue Mar 09 13:31:23 -0800 2010 | |
| |
mongo_mapper.gemspec | Tue Mar 09 13:31:58 -0800 2010 | |
| |
performance/ | Sun Jan 10 18:37:34 -0800 2010 | |
| |
specs.watchr | Sat Jan 09 17:10:28 -0800 2010 | |
| |
test/ | Tue Mar 09 13:20:53 -0800 2010 |
MongoMapper
A Ruby Object Mapper for Mongo.
Releases are tagged on github and released on gemcutter. Master is pushed to whenever I add a patch or a new feature, but I do not release a new gem version each time I push.
Note on Patches/Pull Requests
- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it. This is important so I don’t break it in a future version unintentionally.
- Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself in another branch so I can ignore when I pull)
- Send me a pull request. Bonus points for topic branches.
Install
$ gem install mongo_mapper
Problems or Questions?
Hit up the google group. groups.google.com/group/mongomapper
To see if the problem you are having is a verified issue, you can see the MM pivotal tracker project: www.pivotaltracker.com/projects/33576
There is no need to request to join the Pivotal Tracker project as I am only granting access to a select few (easier to keep things organized). If you have a problem, please use the mailing list. If I confirm it to be a bug, I am happy to add it to PT. Thanks!
Copyright
Copyright © 2009 John Nunemaker. See LICENSE for details.
