-
Notifications
You must be signed in to change notification settings - Fork 3.4k
1. "Error: failed to connect to [localhost:27017]"
MongDB isn't running, please run it before you run grunt...
Consider MongoDB a program that needs to be running before you can run grunt on your MEAN project.
Follow these instructions here for mongodb installation: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-os-x/
Manual Installation is the only manner I could get things working
I also needed to be in /usr/local/bin before I could fire mongod
Once mongod is running in your terminal window, open a different terminal window and cd to the directory where your MEAN project is located.
There you can run a grunt command and avoid the dreaded warning: [nodemon] app crashed - waiting for file changes before starting...
At that point, you can navigate to http://localhost:3000
Mcferren thanks for the explenation
2. "I run grunt but see a white screen with nothing in it"
Either you havn't run npm install or it in turn did not trigger bower install
3. "I run grunt as documented but get a command line not found"
Install grunt-cli globally - npm install grunt-cli -g
4. "I get Error: EMFILE, too many open files” in npm install."
See http://otaqui.com/blog/1618/how-to-fix-error-emfile-too-many-open-files-from-yeoman-and-npm/
- Getting Started Guides
- Deployment
- Testing
- System Deep Dives
Aggregation- Packages
- Database
- Menus
- Circles (roles/permissions) High Level Overview
- Circles code examples
- User Auth withJWT
- Contributing