Convention-based bootstrapper for LoopBack applications
Go to file
Miroslav Bajtoš 3ba43e1197 Pass `app` to fn exported by auto-required script
When a script in `models/` or `boot/` exports a function which is not
a loopback.Model constructor, the bootstrapper immediatelly calls
this exported function wit the current `app` object.

This is providing a dependency injection mechanism for boot scripts,
so that they no longer need to know where to find the `app` object.

Note: the dependency injection is optional. Existing code getting
`app` reference via `require('../app')` will continue to work.
2014-05-27 16:11:54 +02:00
lib Load datasources and app cfg from multiple files 2014-05-27 14:08:58 +02:00
test Pass `app` to fn exported by auto-required script 2014-05-27 16:11:54 +02:00
.gitignore Load datasources and app cfg from multiple files 2014-05-27 14:08:58 +02:00
.jshintignore Custom rootDir for models and datasources 2014-05-27 14:49:11 +02:00
.jshintrc Initial commit 2014-05-23 15:51:20 +02:00
CONTRIBUTING.md Initial commit 2014-05-23 15:51:20 +02:00
LICENSE Initial commit 2014-05-23 15:51:20 +02:00
README.md Initial commit 2014-05-23 15:51:20 +02:00
index.js Pass `app` to fn exported by auto-required script 2014-05-27 16:11:54 +02:00
package.json Load datasources and app cfg from multiple files 2014-05-27 14:08:58 +02:00

README.md

LoopBack Boot

LoopBack Boot is a convention-based bootstrapper for LoopBack applications.

For full documentation, see the official StrongLoop documentation:

Installation

npm install loopback-boot

Usage

TBD