Sails is a large project, with many modular components. Each module is located in its own repository, and in most cases is tested individually.
Below, you'll find an overview of the modules maintained by the core team and community members.
The modules comprising the Sails framework, as well as the other plugins maintained by our core team, are spread across a number of different code repositories. Some modules can be used outside of the context of Sails, while others are not intended for external use.
For more information on the available releases of the Sails framework as a whole, check out the contribution guide.
| Repo | Build Status (edge) | Latest Stable Version |
|---|---|---|
 |
 |
 |
| waterline |  |
 |
| anchor |  |
 |
| waterline-criteria |  |
 |
| waterline-schema |  |
 |
| waterline-utils |  |
|
| sails-generate |  |
 |
| captains-log |  |
 |
| Repo | Latest Stable Version |
|---|---|
| include-all |  |
| reportback |  |
| switchback |  |
As of Sails v1.0, core generators are now bundled in sails-generate. All generators can still be overridden the same way. For examples, see below.
| Hook | Repo | Build Status (edge) | Purpose |
|---|---|---|---|
orm |
sails-hook-orm |  |
Implements support for Waterline ORM in Sails. |
sockets |
sails-hook-sockets |  |
Implements Socket.io support in Sails. |
Other core hooks not listed above are currently contained in sub-folders within Sails core. See
lib/hooks/.
| Repo | Build Status (edge) | Latest Stable Version | Platform |
|---|---|---|---|
| Local Disk |  |
 |
Local disk (.tmp/) |
| MySQL |  |
 |
MySQL |
| PostgreSQL |  |
 |
PostgreSQL |
| Mongo |  |
 |
MongoDB |
| Redis |  |
 |
Redis |
| Platform | Repo | Build Status (edge) |
|---|---|---|
| Browser | sails.io.js |  |
| Node.js | sails.io.js | |
The official documentation for the Sails framework is written in Markdown, and is automatically compiled for the Sails website.
| Repo | Purpose |
|---|---|
| sails-docs | Raw content for reference, conceptual, anatomical, and other documentation on the Sails website (in Markdown). |
| www.sailsjs.org | The Sails app that powers sailsjs.org. HTML content is automatically compiled from sails-docs. |
| doc-templater | The module we use to pre-process, compile, and format Markdown documentation files into the HTML markup and tree menus at sailsjs.org/documentation. |
In addition to the official code repositories that are supported by the Sails.js core team, there are countless other plugins created by members of the Sails.js community.
There are at least 200 community hooks for Sails.js available on NPM.
Need to customize your build? Want automatically-generated spritesheets? Source maps? Sails.js uses Grunt for its asset pipeline, which means it supports any Grunt plugin. out of the box. There are thousands of Grunt plugins available on NPM.
Don't like Grunt? Want to use WebPack or Gulp instead? Prefer your generated backend files to be written in CoffeeScript? There are at least 100 community generators for Sails.js available on NPM.
Learn how to use community generators, and how to build your own.
Is your database not supported by one of the core adapters? Good news! There are many different community database adapters for Sails.js and Waterline available on NPM.
Need to upload files to a cloud file store like S3, GridFS, or Azure Cloud Files? Check out the community filesystem adapters for Sails.js and Skipper available on NPM.
Learn how to wire up one or more custom filesystem adapters for your application.
Need to process payments with Stripe? Fetch video metadata from YouTube? Process user email data via Google APIs? Choose from hundreds of community machinepacks for Sails.js/Node available on NPM.
Learn how to install and use machinepacks in your controller actions and helpers.
Want to work with your database at a low level? Need to get extra performance out of your database queries? Dynamic database connections?
Is EJS bumming you out? Prefer to use a different templating language like pug (/jade), handlebars, or dust? Sails.js supports almost any Consolidate/Express-compatible view engine-- meaning you can use just about any imaginable markup language for your Sails.js views. Check out the community view engines for Sails.js and Express available on NPM.
The recommended production session store for Sails.js is Redis... but we realize that, for some apps, that isn't an option. Fortunately, Sails.js supports almost any Connect/Express-compatible session store-- meaning you can store your sessions almost anywhere, whether that's Mongo, on the local fileystem, or even in a relational database. Check out the community session stores for Sails.js, Express, and Connect available on NPM.
Learn how to install and configure a custom session store in your Sails app.
| Platform | Repo | Build Status (edge) |
|---|---|---|
| iOS | sails.ios |  |
| Android | Sails Messenger | N/A |
| Angular | angularSails |  |
| Objective C | sails.io.objective-c | N/A |
| Backbone | backbone-to-sails | N/A |
| Repo |
|---|
| sails-migrations |
| sails-mysql-transactions |
For easier maintainence, they were pulled into sails-generate.