Bring your Mongoose models straight into angular web app with live Query support, all thanks to the magic of socket.io
Allows to call Mongoose remotely through socket.io-rpc. Usable in browser with any framework-let it be Angular, Aurelia, React or any other. It is also isomorphic, so your client can be another node.js process(nice for midway testing). Offers killer feature(live queries) from Meteor.js for your frontend in a framework agnostic fashion. How? See examples(Angular|Aurelia), if still not sufficent, read source code. Better docs are planned/WIP.
Moonridge is written in commonJS format(client works in node and browser without much hassle), so you need globally installed jspm to be able to install it and run it. If you don't have jspm, install it with this command:
npm i jspm -g
Also currently it requires to have socket.io-rpc installed too. This I will get rid of.
##Basic usage serverside
var mongoose = require'mongoose';var Moonridge = require'moonridge';var MR = moonridgemongoose "mongodb://localhost/moonridge_showcase"; //MongoDB address is optional-you can connect as always with mongoosevar bookModel = MRmodel'book' //mongoose schema defintionname: Stringauthor: String// makes sure only one book per nameXauthor existsschemaindex name: 1 author: 1 unique: true dropDups: true ;;MRbootstrapapp; //app is your express app, Moonridge will start listening on port app.get("port")
##On the CLIENT side with AngularJS: ###HTML
<!--You need to use mr-controller instead of ng-controller--><!--You can load any number of models you like, separate them by commas--><!-- regular angular templating --><!--include client side script after angular-->
//define Moonridge angular module as dependencyangularmodule'app' 'Moonridge'runvar dfd = $qdefer;var url = ''; //your moonridge instance//Moonridge backendvar MRB = $MR'local' dfdpromise true; //true indicates, that this backend should be used by defaultdfdresolveurl: url hs: query: "nick=admin" ; //resolve connects you to the Moonridge backendcontroller'bookCtrl'// create a bookbookcreatename: 'A Game of Thrones' author: 'George R. R. Martin';// query for itvar query = bookqueryfindOneexec;// delete itbookremovequerydoc;//best for last- liveQuery$scopeLQ = bookliveQueryfindexec;//$scope.LQ.docs will contain up to date synced collection of documents that satisfy the query. You can//before exec() you can use any mongoose query method except distinct, remove, update
Also you need to connect to your backend-Moonridge uses a promise resolution for this. See how in the included smoketest
All server-client communication is done with socket.io-rpc -another project of mine, so errors are propagated for all server-side calls which return an error(or reject their promise).
##Supported browsers ###Desktop Internet Explorer 8+ - though it needs es5shim Safari 4+ Google Chrome 4+ Firefox 4+ Opera 10.61+ ###Mobile iPhone Safari iPad Safari Android WebKit WebOs WebKit
One could ask why not just port mongoosejs to the client side and let clients talk to mongo directly. While this would surely be an interesting project, Moonridge has features which would not be possible without a server instance(live querying, custom authorization/authentication). I think these features are worth it introducing a new framework to the backend.
##How does live querying work in one paragraph Every client liveQuery is serialized and sent via socket.io to backend. Backend parses it and constructs real mongoose query, wich is immediately run(if it doesn't exist already in server memory). The return is sent back to client. Any change to a certain document (creation, deletion, update) is checked again for all in-memory queries. MongoDB checks just one recently changed document, not the whole query, so it should be pretty quick. If query is satisfied, the changed document is propagated to listening clients. And that is basically it.
Pull requests are welcome and same goes for issues!