Convention-based bootstrapper for LoopBack applications

Go to file

Miroslav Bajtoš b14800416a Split the boot process into two steps Split bootLoopBackApp into two steps: - compile - execute Most of the changes are just shuffling the existing code around. What has changed: - `loopback.autoAttach()` is called after `models/*` are required. The calls were made in the opposite order before this commit.		2014-06-03 08:13:14 +02:00
docs	Split the boot process into two steps	2014-06-03 08:13:14 +02:00
lib	Split the boot process into two steps	2014-06-03 08:13:14 +02:00
test	Split the boot process into two steps	2014-06-03 08:13:14 +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
CHANGES.md	Start CHANGES.md	2014-05-27 16:18:09 +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
docs.json	Split the boot process into two steps	2014-06-03 08:13:14 +02:00
index.js	Split the boot process into two steps	2014-06-03 08:13:14 +02:00
package.json	Change loopback peer dep to "1.x \|\| 2.x"	2014-05-28 16:03:56 +02:00

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

TBD