heroku/node-js-sample

This repository is deprecated. Head over to https://github.com/heroku/node-js-getting-started

This repository is no longer maintained!

For the most up to date test app to get you started on Heroku, head on over to node-js-getting-started.

---

node-js-sample

A barebones Node.js app using Express 4.

Running Locally

Make sure you have Node.js and the Heroku Toolbelt installed.

git clone [email protected]:heroku/node-js-sample.git # or clone your own fork
cd node-js-sample
npm install
npm start

Your app should now be running on localhost:5000.

Deploying to Heroku

heroku create
git push heroku master
heroku open

Alternatively, you can deploy your own copy of the app using the web-based flow:

Documentation

For more information about using Node.js on Heroku, see these Dev Center articles:

• 10 Habits of a Happy Node Hacker
• Getting Started with Node.js on Heroku
• Heroku Node.js Support
• Node.js on Heroku
• Using WebSockets on Heroku with Node.js

node-js-sample's Issues

怎么连reademe文件都没有呢？我都不知道项目是干什么的。

怎么连reademe文件都没有呢？我都不知道项目是干什么的。

npm-shrink wrap confusing

Is the shrinkwrap file necessary? Imagine my frustration when heroku failed to find a new module I installed and added to package.json, because the shrinkwrap file had already fixed the plugins in time. Took quite a while to realize what was going on.

Is node_modules necessary?

You typically want to add the node_modules directory to your .gitignore file. Keeping dependencies tracked usually isn't necessary when you already have them listed in your package.json.

Anyone cloning the repository should already know (or be instructed to) run npm install after cloning.

Button does not work

Hello!

When I click button in this repo I get:

No app-5c96aa6a5be707f4ff05e1d8c66f0570.json located in the repo URL provided.
Make sure that an app-5c96aa6a5be707f4ff05e1d8c66f0570.json file exists in the project root directory.

centrifugal/centrifugo#14

Update to Node 0.12.x

node-js-sample fails git push due to shrinkwrap hard coded ip address host down

The hard coded ip address in npm-shrinkwrap.json is not responding. This results in git push to fail with a timeout error message after a long delay.

remote: -----> Building dependencies
remote: Pruning any extraneous modules
remote: Installing node modules (package.json + shrinkwrap)
remote: npm ERR! fetch failed http://174.129.255.150:4873/mime-types/-/mime-types-2.0.10.tgz
remote: npm ERR! fetch failed http://174.129.255.150:4873/mime-types/-/mime-types-2.0.10.tgz
remote: npm ERR! fetch failed http://174.129.255.150:4873/mime-types/-/mime-types-2.0.10.tgz
remote: npm ERR! Linux 3.13.0-61-generic
remote: npm ERR! argv "/tmp/build_255e09f531e5b58d25519c3549f33d3e/.heroku/node/bin/node" "/tmp/build_255e09f531e5b58d25519c3549f33d3e/.h
eroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_255e09f531e5b58d25519c3549f33d3e/.npmrc"
remote: npm ERR! node v0.12.2
remote: npm ERR! npm v2.7.4
remote: npm ERR! code ETIMEDOUT

I tried to ping the host and it appears down:

[0 ubuntu@somehost ~/proj/bitstarter]$ nmap -p 4873 174.129.255.150
Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-28 12:42 PDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.03 seconds

The host appears to be an aws ip:
150.255.129.174.in-addr.arpa domain name pointer ec2-174-129-255-150.compute-1.amazonaws.com

Can we please have this fixed so we can get on with our heroku learning? ;) This was working like 1-2 weeks ago.

Update nodejs version

Maybe 8.12.0 at least.

Missing logo in app.json

Looks like the logo linked in https://github.com/heroku/node-js-sample/blob/master/app.json#L5 is no longer available, which results in a broken image when using this repo and deploying via Heroku Button.

cc @hunterloftis @jmorrell

Why package.json and app.json?

These two files have significant content overlap. What is the reason or purpose for having both?