Harry Wolff f16dc290b7 Improve bootstrap flow of a Ghost application ... addresses #1789, #1364 - Moves ./core/server/loader -> ./core/bootstrap. The bootstrap file is only accessed once during startup, and it’s sole job is to ensure a config.js file exists (creating one if it doesn’t) and then validates the contents of the config file. Since this is directly related to the initializing the application is is appropriate to have it in the ./core folder, named bootstrap as that is what it does. This also improves the dependency graph, as now the bootstrap file require’s the ./core/server/config module and is responsible for passing in the validated config file. Whereas before we had ./core/server/config require’ing ./core/server/loader and running its init code and then passing that value back to itself, the flow is now more straight forward of ./core/bootstrap handling initialization and then instatiation of config module - Merges ./core/server/config/paths into ./core/server/config This flow was always confusing me to that some config options were on the config object, and some were on the paths object. This change now incorporates all of the variables previously defined in config/paths directly into the config module, and in extension, the config.js file. This means that you now have the option of deciding at startup where the content directory for ghost should reside. - broke out loader tests in config_spec to bootstrap_spec - updated all relevant files to now use config().paths - moved urlFor and urlForPost function into ./server/config/url.js		2014-02-07 17:34:21 -05:00
..
index.js	Replace underscore with lodash.	2014-02-06 14:08:34 +00:00
loader.js	Improve bootstrap flow of a Ghost application	2014-02-07 17:34:21 -05:00
proxy.js	Replace underscore with lodash.	2014-02-06 14:08:34 +00:00
sandbox.js	Replace underscore with lodash.	2014-02-06 14:08:34 +00:00