Consider structure that makes it easier to mount sub-ezel projects

[craigspaeth]

See: https://twitter.com/craigspaeth/status/489061988257910784

Currently it's difficult b/c we override Backbone's sync at the larger project level, then expect models/collections to use that one backbone module. However, sub-apps under node_modules can have their own dependencies and can use their own version of Backbone without a modified sync. In this case we want a sane approach to have both apps use a modified sync. This kind of isolation/vs. shared setup conundrum can also occur in the need to share config/sharify data.

Options could include:

• Pass in Backbone/config/sharify in a sort-of dependency injection manner to sub-apps. e.g. app.use(require('ezel-sub-app')(Backbone, config, sharify));
• Sub-apps require backwards into the main project e.g. Backbone = require('../../node_modules/backbone')
• Some kind of mount helper function that can modify a sub-app based on the project setup.

None of these seem too appealing though.