A suite of examples written for Sails.js, AngularJS, and Twitter Bootstrap.
- A REST API test page using Sails' transport agnostic routing (HTTP vs. Socket.io)
- A "Todo List" app demo using Sails' Socket.io messaging and REST Blueprints
- Passport middleware authentication integrated with Sails policies.
- Twitter Bootstrap / Font Awesome custom LESS compiles (Grunt)
- Cache busting JS/CSS for production (Grunt)
If there other examples you would like to see, feel free to create a GitHub issue.
(as of May 5, 2014)
Updated to latest Sails.js version
0.9.16 and added some fixes for
config/500.js file has changed to include a 4th parameter to notify express'
middleware that it is an error handler. Several jade files have also been edited to remove the
!!! deprecated doctype.
This fixes the html views for 404 and 500 error pages, as well as the oddity I had seen in January with 500 errors on
the API test page. The 403 forbidden errors are still inconsistent between HTTP and Socket modes (???).
(as of Jan 7, 2014)
Be wary, this repo has been quickly hacked together as a Sails.js/AngularJS learning project. Do not consider it as production-ready code.
REST API example page (see
This API test page was primarily made to exercise the error handling of REST calls between HTTP and Socket modes (404, 403, 500 errors). I am currently seeing some odd behavior when throwing 500 application errors, and when 403 forbidden errors are triggered from policy configurations. The results are not consistent between modes. More research is needed.
Todo List app demo (see
This demo was written to explore how the socket.io connection, comet messages,
and auto-subscriptions work in Sails. The
examples were used a bit for reference. The Sails socket.io code, which is
provided during creation of a new Sails project, was refactored into an Angular
assets/linker/js/angular-sails.io.js). It contains custom retry
logic that first sends a
$http.get() request to the server for obtaining the
security token cookie, otherwise you may encounter the
500 error: "handshake error" when restarting your local server
(See bottom of: FAQ).
If you stop the server or cause a network disconnect when on the example pages,
you should see some alert modals pop up. These are managed by SailsSocketCtrl
assets/linker/js/controllers/sailsSocketCtrl.js) for reuse across examples.
Credit goes to this gist and its many forks.
You can log in using the dummy user/pass:
Here are the files that were touched:
api/controllers/PassportAuthController.js api/models/User.js api/policies/isPassportAuthenticated.js config/bootstrap.js config/express.js config/policies.js config/routes.js views/passportauth/login.jade views/passportauth/protected.jade
The Sails.js asset grunt tasks have been reconfigured to allow Twitter Bootstrap
and Font Awesome custom compiles (see
copy task has also been reconfigured to include other Bower-managed
You may also like...
sailsCasts : A great series of screencasts showing you how to use Sails.js.
The levid/angular-sails-socketio-mongo-demo repo may also be of interest for Sails v0.8 users.
Maarten de Boer is working on a Sails v0.10 and AngularJS tutorial: maartendb/angular-sails-scrum-tutorial
- Sails.js v0.9
- Twitter Bootstrap v3
- AngularJS v1.2
- Angular-UI Bootstrap
- Font Awesome
- Jade Templates
Node v0.10.x (brcypt is failing to compile in v0.12 at the moment)
Ensure that sails and bower are installed:
sudo npm -g install sails bower
Clone this repo:
git clone https://github.com/cgmartin/sailsjs-angularjs-bootstrap-example.git
bower to install all dependencies:
cd sailsjs-angularjs-bootstrap-example npm install ; bower install
Lift the server:
And then visit (http://localhost:1337/) to run the examples.
MIT License Copyright © 2014 Christopher Martin