support for disabled modules, multiple database connections, lazy models creation, further implementation of core modules according to original idea given by Andrija Petrovic, support for submenu items ...

First of all, thank you for a fantastic project you have delivered to us :D I hope I will be able to help a bit.
Few things has been addressed here:
1. support for module disabling. Adding disabled_modules list in configuration file will allow module loader to skip loading specified modules allowing developers to turn off modules got from repo without messing with original repo structure avoiding, that way, problems with pulling latest changes.
2. multiple mongo DB connections situation. Adding dbs map in configuration file in format db_alias:connection_path will create connections to given mongodb paths. Once connecting databases is done, two functions are added to mongoose instance in order to make connection map available to outer world: 
 * get_MEANIODB_connection : which will return connection for given db_alias. If record in map, default connection is returned
 * alias_MEANIODB_exists: helper function which allows to check if alias has been registered.

After setting these functions, rest of bootstrap is done so these functions remains visible to the rest of program ...
3. model loading helper has been introduced. It is backward compatible to support current implementation. If model.js file set to module.exports register field with model settings, model will be registered within requireModel function. This way, model file writer has some typing help: with previous solution, programmer should, in every model write something like this 
```javascript
mongoose.get_MEANIODB_connection(dbalias).model(model, schema, [collection])
```
With this solution model programmer should set : 
```javascript
module.exports = {
  register : [
    { schema: UserSchema, model: 'User', dbs:['users'] }
  ]
};
```
and requireModel function will do rest of job ...
On the other hand if UserSchema is a simple hash, not instance of mongoose.Schema, lazy model creation is invoked. This way every file invoked through module load process can extend schema object. Once all modules are loaded, lazy models creation is started: createModels will take resulting structure and create schema and model on designated db connection out of it ... 
4. Last (for now) but not least, core modules has been implemented as far as possible ...

Best regards ...