background preloader


Facebook Twitter

MongoAdmin. Introducing a new admin interface for MongoDB, written in Python using Django and Bootstrap.


Features Beautiful interface with Bootstrap. Flexible JSON object editor on JavaScript that supports editing nested objects. Filter collections with a query and specify the columns to show. Screenshots Code Get the code from GitHub ( git clone Alternatively, download mongoadmin_project-0.1.tar.bz2 (v0.1, revision 472d30a). Getting started Make sure you have the following packages installed: Django 1.4 mongo-python-driver Make a copy the included default project settings: cp mongoadmin_project/ mongoadmin_project/ Create a database for Django (by default, it is a MySQL database called mongoadmin, but you can change it in DATABASES in the settings). Fill in SECRET_KEY (can be any random string) in the file that you created. Create SQL database tables: python syncdb Run the server: python runserver Go to and connect to your Mongo database.

License Great! Hi, [ Popular Links: mongoDB ~ the good to begin links. Production Deployments. MongoDB, Morphia and EmbedMongo » The Cubeia Blog. Most of the times when working with online games we run into the need to persist data that is produced by the games.

MongoDB, Morphia and EmbedMongo » The Cubeia Blog

This can be anything from hand history to game state to audit trails for remote calls to other systems. But what they usually have in common is that it is high volume writes, hardly any updates, some reads and that the data has large variation in what we need to store even if it is within the same context. That last part about the data having variations is what makes this interesting. Take hand history for instance, we want to save events that are executed on a Poker table. On a Poker table many things happens – player join and leave the table, bets are made, cards are dealt, players get more chips etc. etc. If we were to use a relational database we might end up with a single table with an ungodly amount of columns so that each event has all its specific columns available. But what about this NOSQL stuff I have heard so much about? So I chose to go with MongoDB. @Entity. You Only Wish MongoDB Wasn't Relational. MongoDB = Get Stuff Done Update: Changed blog example to use a normal belongs-to relationship.

You Only Wish MongoDB Wasn't Relational

Update: Added examples of $slice and $elemMatch to show why they don’t work When choosing the stack for our TV guide service, we became interested in NoSQL dbs because we anticipated needing to scale horizontally. We evaluated several and settled on MongoDB. The main reason was that MongoDB got out of the way and let us get work done. So when you read that MongoDB is a document store, you might get the wonderful idea to store your relationships in a big document. Several times, we’ve excitedly begun a schema this way, only to be forced to pull the nested documents out into their own collection. Let’s make a blog! Here’s an example. What’s a blog without comments? This works nicely with the key/value idea that you should denormalize your data. When Nested Documents Become a Problem.

The Little MongoDB Book

The MongoDB Collection. MongoDB Interactive Tutorial. MongoDB. MongoDB | node.js - Plugins/Etc.