-
Notifications
You must be signed in to change notification settings - Fork 239
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
Unable to create DB #1
Comments
Can you post what your config.json file looks like? |
{ |
The problem is, you need to surround chuck in quotes, like "chuck" similar to how "postgres" or "postman_dev". |
Excellent that worked. Thank you ! |
What error are you getting? |
Nevermind, fixed it. Thanks. |
Unable to create DB. Reference below for the error. Please advise.
ERROR: Error reading "server\config\config.json". Error: SyntaxError: C:\Users\Charles\Desktop\Postman\postman-master\server\config\config.json: Unexpected token c in JSON at position 65
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! postman@0.0.0 db:create:
sequelize db:create && npm run db:migrate && npm run db:seed
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the postman@0.0.0 db:create script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Charles\AppData\Roaming\npm-cache_logs\2018-01-03T01_46_34_576Z-debug.log
C:\Users\Charles\Desktop\Postman\postman-master\server\config>npm install
openssl config failed: error:02001003:system library:fopen:No such process
npm WARN rollback Rolling back node-pre-gyp@0.6.36 failed (this is probably harmless): EPERM: operation not permitted, rmdir 'C:\Users\Charles\Desktop\Postman\postman-master\node_modules\fsevents\node_modules'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
The text was updated successfully, but these errors were encountered: