-
Notifications
You must be signed in to change notification settings - Fork 35
confidence/glue support #64
Comments
I'm vaguely familiar with glue. It sounds like there isn't much we can do about that besides going back to having the plugin manage building up the Sequelize instance during registration again. Is this the case or are there any work arounds? |
That's precisely the case, depending on |
That's how the plugin used to work before I did a complete rewrite (v3). Too tired to try and come up with a list of cons right now but my goal was to decouple Sequelize from the plugin and just make the plugin a lot simpler and more flexible overall. I have no interest in going back to that at this moment but I will take a look at this issue later and weigh the options |
The work around is registering an internal plugin that in-turn registers ./server/app-start/hapi-sequelize/index.js:
./server/database/index.js:
./server/manifest.js:
|
You can just do; let manifest = require('./config/manifest');
manifest.registrations.push({
"plugin": {
"register": "hapi-sequelize",
"options": {
"name": "name",
"models": 'models/models/*.js',
"sequelize": new Sequelize(db_string, {
}),
"sync": true,
"forceSync": false
}
}
})
// Load the manifest and start the server This loads the module correctly for me. hapi-sequelize v3.0.4 and glue 4.0.0 |
Passing the sequelize instance in the options does not work with confidence and glue as the composer requires the manifest to be valid JSON.
The text was updated successfully, but these errors were encountered: