This template exists to make it easier for you to get started writing an official adapter for Sails.js.
It's usually pretty easy to add your own adapters for integrating with proprietary systems or existing open APIs. For most things, it's as easy as
require('some-module') and mapping the appropriate methods to match waterline semantics. To get started:
- Fork this repository
- Set up your README and package.json file. Sails.js adapter module names are of the form sails-*, where * is the name of the datastore or service you're integrating with.
- Build your adapter.
How to test your adapter
npm linkin this adapter's directory
- Clone the sails.js core and modify the tests to use your new adapter.
npm link sails-boilerplate
- From the sails.js core directory, run
Submitting your adapter
- Do a pull request to this repository (make sure you attribute yourself as the author set the license in the package.json to "MIT") Please let us know about any special instructions for usage/testing.
- We'll run the tests one last time. If there are any issues, we'll let you know.
- When it's ready, we'll update the documentation with information about your new adapter
- Then we'll tweet and post about it on our blog, adoring you with lavish praises.
- Mike will send you jelly beans.
About Sails.js and Waterline
Waterline is a new kind of storage and retrieval engine for Sails.js. It provides a uniform API for accessing stuff from different kinds of databases, protocols, and 3rd party APIs. That means you write the same code to get users, whether they live in mySQL, LDAP, MongoDB, or Facebook.