New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
current architecture does not generate migration files #34
Comments
@pauloladimeji Sorry for the late response... Thank you 😀 I am glad that I could help you... I never really worked with sequelize-cli... Could you provide some information on how we had to change our current architecture? How would the file system look like? What would be the best way to integrate sequelize-cli in your opinion? |
hello, i am using this boilerplate with sequelize-cli i'm just init the sequelize in the project. then create this file .sequelizerc on root directory and change the code inside into `const path = require('path'); module.exports = { then the cli working as expected. notes: |
Thanks! @aichbauer and @ace3 ... I am also using a setup similar to @ace3's ... migration and seeds are why I use the cli as well... |
Has anyone tried using sequelize-auto-migrations?
The error is
|
Same error here |
first off, thanks for this boilerplate! helped me in many ways.
using sequelize-cli automatically generates models and migration files. since this boilerplate doesn't make use of sequelize-cli, models and their associations need to be defined manually.
i'm considering integrating sequelize-cli myself, but i don't know how much it will mess with the file dependencies using the current architecture?
are there any plans to upgrade to using sequelize-cli?
The text was updated successfully, but these errors were encountered: