-
Shouldn't deploying a node app
my logs say
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Is the |
Beta Was this translation helpful? Give feedback.
-
Yes, I have a
Re-deploying didn't work. So I rebuilt it.
which seems to have kicked off the npm install! I think the troubles started because I didn't have node installed on the server. Even after I installed node manually, and re-deploying, npm install didn't run. So the destroy seems to have fixed things.
the package.json {
"name": "node-js-sample",
"version": "0.2.0",
"description": "A sample Node.js app using Express 4",
"main": "index.js",
"scripts": {
"start": "node index.js"
},
"dependencies": {
"express": "^4.13.3"
},
"engines": {
"node": "4.0.0"
}, Procfile
Git However I'm not sure how to access the app on my vmware server, and on what port? I'm used to using
Am a bit worried about the log messsage
can't seem to find any documentation on this. Not sure why I need to do anything extra, surely express should be handling all of this. |
Beta Was this translation helpful? Give feedback.
-
That depends on how you use ( And don’t worry about the “no request plugin” warning, that is because there is no plugin loaded inside (Final edit: moved to discussions) |
Beta Was this translation helpful? Give feedback.
Yes, I have a
package.json
- its the same node sample project I deploy to dokku, for testing.Re-deploying didn't work. So I rebuilt it.
which seems to have kicked off the npm install! I think the troubles started because I didn't have node installed on the server. Even after I installed node manually, and re-deploying, npm install didn't run. So the destroy seems to have fixed things.