concept credential in category sails

This is an excerpt from Manning's book Sails.js in Action.
For example, if you use the User.find() method to find a particular record, this option tells Sails which database to search. The connection points to a dictionary that contains configuration information like the host, port, and credentials necessary to access the database. If any of that sounds unfamiliar, don’t worry—we’ll come back to it a few times throughout the book. Another model setting, migrate, designates how Sails should handle existing records in the database and whether or not to use auto-migration. As a final example, the schema setting allows you to enforce the use of a schema, even if the underlying database would allow you to proceed without one. This is particularly useful for schemaless databases like MongoDB.
Using brushfire/config/local.js during development was a convenient way of storing credentials locally. That, combined with using brushfire/.gitignore, prevented the local.js file from being pushed to your remote repository, thereby effectively preventing sensitive data from being pushed to a public repository. Now that you’re deploying Brushfire to Heroku, there’s an issue of where and how to store these credentials. You’ll store the credentials on Heroku and access them securely in Sails using environment variables.