   # PUT    /foos/:id?
   # DELETE /foos/:id?
   pluralize: false
-  
+
   # Whether the blueprint controllers should populate model fetches with
   # data from other models which are linked by associations
-  
+
   # If you have a lot of data in one-to-many associations, leaving this on
   # may result in very heavy api calls
   populate: true

  #
  # By default, no prefix is used.
  prefix: ""
  
  # Whether to pluralize controller names in blueprint routes.
  #
  # (NOTE: This only applies to blueprint autoroutes, not manual routes from `sails.config.routes`)

http://links.sailsjs.org/docs/config/blueprints
###
module.exports.blueprints =

  ###
  NOTE:
  A lot of the configuration options below affect so-called "CRUD methods",
  or your controllers' `find`, `create`, `update`, and `destroy` actions.

  It's important to realize that, even if you haven't defined these yourself, as long as
  a model exists with the same name as the controller, Sails will respond with built-in CRUD
  logic in the form of a JSON API, including support for sort, pagination, and filtering.
  ###


  # Action blueprints speed up the backend development workflow by eliminating the need
  # to manually bind routes. When enabled, GET, POST, PUT, and DELETE routes will be
  # generated for every one of a controller's actions.
