forked from balderdashy/sails
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add explanation of why custom paths need to be configured in sailsrc,…
… programmatically, or using env variables
- Loading branch information
1 parent
6bd6f80
commit fdf3ffb
Showing
1 changed file
with
3 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,8 @@ | ||
## Moduleloader Hook | ||
|
||
This hook loads modules from your configured directories in sails.config.paths. It is always loaded first or second. | ||
This hook loads modules from your configured directories in `sails.config.paths`. It is always loaded first or second. | ||
|
||
> Note that consequently, in order to customize `sails.config.paths`, you need to inject configuration into the load process using env variables, the .sailsrc file, or by passing in an option to the programmatic call to sails.lift (i.e. in app.js). Otherwise, by the time your user configuration files in config/* have loaded, it is too late (this hook has already run using the default paths). | ||
##### Contributing to this hook | ||
Not a good place to jump in right now. Please tweet @mikermcneil before working on this part! |