-
Notifications
You must be signed in to change notification settings - Fork 563
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
setting up postgres, running sequelize init #207
Comments
Ah. I had to cd into I would close this and submit a PR to the docs, but that Do you think there is some way to explain this in the docs and or restructure the sequelize config? |
@WestleyArgentum Thanks for creating this issue. Interesting. When I was running through this docs with a fresh clone, I didn't have to run @mjewell might have more context to this issue. 🍶 |
Hey, For me just running Regardless, if you do want to run the command you were trying, you will have use a slightly different syntax due to the way npm scripts handle args. If you look here it explains it, but the TL;DR is |
Oh my gosh, I'm sorry, at some point I must have copied files over in osx finder and thereby lost all the .files Thanks very much, sorry for the noise |
Haha, no problem. Glad it's all working |
I've tried all the ways mentioned here and keep getting: Sequelize [Node: 10.1.0, CLI: 2.8.0, ORM: 3.30.4] (node:4737) ExperimentalWarning: The fs.promises API is experimental Anyone have any idea what is going wrong? |
I'm having trouble setting up postgres.
I've followed the docs, set up my database, run
But when I try to run
npm run sequelize db:migrate
, I get an error saying that I should runsequelize init
.Fair enough, so I do that, but then it creates a new config and empty folders for migrations, etc.
Looking in
./server/db/sequelize
I see the migrations I think I'm supposed to be using... but I'm at a loss as to how to configure sequelize to use them...Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: