Skip to content

Latest commit

 

History

History
47 lines (32 loc) · 3.14 KB

config.md

File metadata and controls

47 lines (32 loc) · 3.14 KB

#Config

###Contents: ####404

The default 404 handler.

####500

The default 500 error handler.

####Adapters

The adapters configuration object lets you create different global “saved settings” that you can mix and match in your models.

####Bootstrap

This is an asynchronous boostrap function that runs before your Sails app gets lifted (i.e. starts up). This gives you an opportunity to set up your data model, run jobs, or perform some special logic.

####Controllers

By default, Sails controllers automatically bind routes for each of their functions. Additionally, each controller will automatically bind routes for a CRUD API controlling the model which matches its name, if one exists.

####CSRF

When enabled, all non-GET requests to the Sails server must be accompanied by a special token, identified as the '_csrf' parameter.

####Express

If you want to use custom middleware or add local variables and helpers to templates you can do so by configuring express in this config file.

####Local

While you’re developing your app, this config file should include any settings specifically for your development computer (db passwords, etc.)

####Locales

This is a folder that contains the Language files for different locales.

####Log

The logger file configures the log level for your app, as well as the transport.

####Policies

Policies are like any other system for authentication control. You can allow or deny access in fine granularity with policies.

####Routes

Sails uses a number of different strategies to route requests. This section lists them top-to-bottom, in order of precedence.

####Session

Sails session integration leans heavily on the great work already done by Express, but also unifies Socket.io with the Connect session store.

####Sockets

These configuration options provide transparent access to Sails’ encapsulated pubsub/socket server for complete customizability.

####Views

Server-sent views are a classic and effective way to get your app up and running. Views are normally served from controllers, but by default, Sails also exposes routes to allow you to preview your viewsn in a browser.