loopback-example-offline-sync
An example running LoopBack in the browser and server, demonstrating the following features:
- offline data access and synchronization
- routes shared between the AngularJS app and the HTTP server
Install and Run
-
You must have
nodeandgitinstalled. It’s recommended to havemongodinstalled too, so that the data is preserved across application restarts. -
Clone the repo.
-
cd loopback-example-offline-sync -
npm install- install the root package dependencies. -
npm install grunt-cli -g- skip if you have Grunt CLI already installed. -
npm install bower -g- skip if you already have Bower installed. -
bower install- install front-end scripts -
mongod- make sure mongodb is running if you want to run withNODE_ENV=production. -
grunt serve- build and run the entire project in development mode. -
open
http://localhost:3000- point a browser at the running application.
Project layout
The project is composed from multiple components.
-
common/models/contains definition of models that are shared by both the server and the client. -
client/lbclient/provides an isomorphic loopback client with offline synchronization. The client needs some client-only models for data synchronization. These models are defined inclient/lbclient/models/. -
client/ngapp/is a single-page AngularJS application scaffolded usingyo angular, with a few modifications to make it work better in the full-stack project. -
server/is the main HTTP server that brings together all other components. Also сontains the REST API server; it exposes the shared models via REST API.
Build
This project uses Grunt for the build, since that’s what
yo angular creates.
There are three major changes from the generic Gruntfile required for this full-stack example:
-
grunt serveuses theserver/component instead ofgrunt connect. -
lbclientcomponent provides a custom build script (lbclient/build.js) which runsbrowserifyto produce a single js file to be used in the browser. The Gruntfile contains a custom task to run this build. -
The definition of Angular routes is kept in a standalone JSON file that is used by the
server/component too. To make this JSON file available in the browser, there is a custom task that buildsngapp/config/bundle.js.
Targets
grunt servestarts the application in development mode, watching for file changes and automatically reloading the application.grunt testruns automated tests (only the front-end has tests at the moment).grunt buildcreates the bundle for deploying to production.grunt serve:diststarts the application serving the production bundle of the front-end SPA.grunt jshintchecks consistency of the coding style.
Adding more features
Define a new shared model
The instructions assume the name of the new model is ‘MyModel’.
-
Create a file
models/my-model.json, put the model definition there. Usemodels/todo.jsonas an example, see loopback-boot docs for more details about the file format. -
(Optional) Add
models/my-model.jsand implement your custom model methods. Seemodels/todo.jsfor an example. -
Add an entry to
rest/models.jsonto configure the new model in the REST server:{ "MyModel": { "dataSource": "db" } } -
Define a client-only model to represent the remote server model in the client - create
lbclient/models/my-model.jsonwith the following content:{ "name": "RemoteMyModel", "base": "MyModel" } -
Add two entries to
lbclient/models.jsonto configure the new models for the client:{ "MyModel": { "dataSource": "local" }, "RemoteMyModel": { "dataSource": "remote" } } -
Register the local model with Angular’s injector in
ngapp/scripts/services/lbclient.js:.value('MyModel', app.models.LocalMyModel)
Create a new Angular route
Since the full-stack example project shares the routes between the client and the server, the new route cannot be added using the yeoman generator.
-
(Optional) Create a new angular controller using yeoman, for example,
$ yo angular:controller MyModel -
(Optional) Create a new angular view using yeoman, for example,
$ yo angular:view models -
Add a route entry to
ngapp/config/routes.json, for example,{ "/models": { "controller": "MymodelCtrl", "templateUrl": "/views/models.html" } }