-
Notifications
You must be signed in to change notification settings - Fork 0
Home
verwebbt edited this page Nov 23, 2014
·
4 revisions
- Start in development environment:
npm start- No authorization
- Requests made as not authenticated fake user
- Start in production environment:
npm run productionorNODE_ENV=production npm start- With authorization (Google)
- Access token generated by the osx client or the playground
If anything fails and everything sucks, check this before you freak out:
-
mongodis running - old mongo collections (= tables) are deleted
- old mongo documents (= entries) are deleted
- sssnap-server is up-to-date
- node dependencies are installed with
npm installornpm update
Some hints:
| Message | Reason | Solution |
|---|---|---|
After start: [Error: failed to connect to [localhost:27017]]
|
Can't connect to mongoDB | run mongod
|
After start, in npm error message, 3rd line: Error: Cannot find module '[name]'
|
Dependency isn't installed | run npm install. If error still exists: npm install [name] and open an issue |
| While running: mongodb error, something with multiple key | Most likely: old schema in collection | Look up which collection caused the error, then: mongo > use sssnap > db.collection.drop(). Replace collection with name of collection. |