New Relic instrumentation for Moped (1.x, 2.0) / Mongoid (3.x, 4.0)

Just like a database has a query language like SQL this is a query language specifically for answering questions about probabilities of events based on the samples you have seen before

This gem can be used to allow the CASino backend to authenticate against an MongoDB server using Moped.

Mongoid Middleware for Sidekiq

LocomotiveCMS is a next generation CMS system with sexy admin tools, liquid templating, and inline editing powered by mongodb and rails 3.2

Makes it easy to use money with mongoid

Transparently store MongoDB ObjectId values in ActiveRecord.

Transparently store MongoDB ObjectId values in ActiveRecord.

Log your moped queries with ActiveSupport::Notifications.instrument calls

Saves space by storing strings with limited character sets as packed BSON BinData.

Take the sting out of building complex MongoDB queries, updates and aggregations.

Strategies for cleaning databases using Moped. Can be used to ensure a clean state for testing.

Dragonfly data store that uses Moped::GridFS.

电子书工具集.

EM-Synchrony-Moped is a Moped driver patch for EM-Synchtony, allowing your asynchronous application use non-blocking connections to MongoDB. Moped is the MongoDB driver for the Mongoid ORM.

Make database queries available via HTTP

Rails I18n backend for MongoDB

Jamnagar is a library for processing content using an petroleum refinement metaphor.

Json web token, setting data to header

When you have a project in which you are not using Mongoid::Timestamps and you want to mock an object's creation time, you have to do some cumbersome operations in order to get those first 4 bytes of the ObjectId to represent the seconds since the Unix epoch that you want for that object. Particularly, if you want to have two objects with the same creation time, it would not suffice to generate the IDs via the BSON::ObjectId.from_time method, since it would yield the same ID for both objects, and you probably do not want them to be seen as the same object. This gem solves this little annoying issue by generating a unique ID for the given timestamp by using the other 8 bytes in ObjectId to generate the needed additional entropy.