Uploading project node.js (with websocket) to Heroku

Question

Uploading project node.js (with websocket) to Heroku

Navigation

#1 by (1 votes)

1

The project is this: link

I followed all these steps:

Heroku login

ssh-keygen -t rsa

heroku keys:add

Procfile 
(web: tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=$PORT --tilePort=$PORT --tiles=./tiles)

heroku create

heroku labs:enable websockets

git remote add heroku [email protected]:seu-app-name.git

git push heroku master

-----> Writing a custom .npmrc to circumvent npm bugs
-----> Exporting config vars to environment
-----> Installing dependencies
       npm WARN package.json [email protected] No repository field.
       npm WARN package.json [email protected] No repository field.
       npm WARN package.json [email protected] No repository field.
-----> Caching node_modules directory for future builds
-----> Cleaning up node-gyp and npm artifacts
-----> Building runtime environment
-----> Discovering process types
       Procfile declares types -> web

-----> Compressing... done, 14.2MB
-----> Launching... done, v3
       http://neuberfranlights.herokuapp.com/ deployed to Hero

Gypsy

root@coder:/backup# heroku logs
2014-06-05T15:13:03.928437+00:00 heroku[api]: Enable Logplex by [email protected]
2014-06-05T15:13:03.929255+00:00 heroku[api]: Release v2 created by [email protected]
2014-06-05T15:19:23+00:00 heroku[slug-compiler]: Slug compilation started
2014-06-05T15:19:46+00:00 heroku[slug-compiler]: Slug compilation finished
2014-06-05T15:19:49.610513+00:00 app[web.1]: bash: tilestream: command not found
2014-06-05T15:19:46.624287+00:00 heroku[api]: Deploy c20c9f1 by [email protected]
2014-06-05T15:19:46.504770+00:00 heroku[api]: Scale to web=1 by [email protected]
2014-06-05T15:19:46.624389+00:00 heroku[api]: Release v3 created by [email protected]
2014-06-05T15:19:50.775922+00:00 heroku[web.1]: State changed from starting to crashed
2014-06-05T15:19:50.776898+00:00 heroku[web.1]: State changed from crashed to starting
2014-06-05T15:19:50.765465+00:00 heroku[web.1]: Process exited with status 127
2014-06-05T15:19:48.908599+00:00 heroku[web.1]: Starting process with command 'tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=37916 --tilePort=37916 --tiles=./tiles'
2014-06-05T15:19:53.891031+00:00 heroku[web.1]: Starting process with command 'tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=42142 --tilePort=42142 --tiles=./tiles'
2014-06-05T15:19:55.656337+00:00 app[web.1]: bash: tilestream: command not found
2014-06-05T15:19:57.470998+00:00 heroku[web.1]: State changed from starting to crashed
2014-06-05T15:19:57.459609+00:00 heroku[web.1]: Process exited with status 127
2014-06-05T15:20:01.414382+00:00 heroku[router]: at=error code=H10 desc="App cra
shed" method=GET path=/ host=neuberfranlight2.herokuapp.com request_id=b2e526cd-0c83-43f1-9e18-c948a7dc7739 fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:20:01.931195+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlight2.herokuapp.com request_id=e532137a-9bd4-4d5e-9484-7b632d325457 fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:20:02.152067+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlight2.herokuapp.com request_id=1bcc67d0-ba41-40d6-9d7b-13dd2913f17c fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:20:06.511712+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlight2.herokuapp.com request_id=5d4a803c-4879-41b8-bc19-b2af7676da65 fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:25:10.643786+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlights.herokuapp.com request_id=a942c3a7-7932-461d-9974-1ca025f0a18c fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:25:11.060255+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlights.herokuapp.com request_id=c5c8a91a-48a9-4f8d-ba60-83e604e9e206 fwd="177.106.83.32" dyno= connect= service= status=503 by
tes=
2014-06-05T15:25:11.287877+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlights.herokuapp.com request_id=b34b2122-ce2c-40db-b67f-7ebcaf83d80e fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:26:37.513012+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlights.herokuapp.com request_id=3c41e3ee-9275-4bb7-b452-9d1f7fd1979d fwd="177.106.83.32" dyno= connect= service= status=503 bytes=
2014-06-05T15:43:09.958789+00:00 heroku[web.1]: State changed from crashed to starting
2014-06-05T15:43:14.298030+00:00 app[web.1]: bash: tilestream: command not found
2014-06-05T15:43:15.821049+00:00 heroku[web.1]: State changed from starting to crashed
2014-06-05T15:43:15.809989+00:00 heroku[web.1]: Process exited with status 127
2014-06-05T15:43:12.922824+00:00 heroku[web.1]: Starting process with command 'tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=26787 --tilePort=26787 --tiles=./tiles'
2014-06-05T16:01:11.305215+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlights.herokuapp.com request_id=9c533405-77ae-42e3-8dd2-36c054133ef6 fwd="146.164.9.138" dyno= connect= service= status=503 bytes=
2014-06-05T16:01:12.357053+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlights.herokuapp.com request_id=3b4d59e2-be06-4a82-8e9a-acdce5f57a7f fwd="146.164.9.138" dyno= connect= service= status=503 bytes=
2014-06-05T16:11:18.785280+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlights.herokuapp.com request_id=99500615-0d79-4f44-be95-534eb89e68c5 fwd="54.237.214.217" dyno= connect= service= status=503 bytes=
2014-06-05T16:25:34.524432+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlights.herokuapp.com request_id=1eb005a1-22fe-4e7e-b713-badf4bd6e411 fwd="200.229.198.131" dyno= connect= service= status=503 bytes=
2014-06-05T16:25:35.703204+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlights.herokuapp.com request_id=a87b8a35-73b7-402f-8bca-19e5bcb61082 fwd="200.229.198.131" dyno= connect= service= status=503 bytes=
2014-06-05T16:51:06.670209+00:00 heroku[web.1]: State changed from crashed to starting
2014-06-05T16:51:10.040070+00:00 app[web.1]: bash: tilestream: command not found
2014-06-05T16:51:11.312395+00:00 heroku[web.1]: State changed from starting to crashed
2014-06-05T16:51:09.090355+00:00 heroku[web.1]: Starting process with command 'tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=51353 --tilePort=51353 --tiles=./tiles'
2014-06-05T16:51:11.301487+00:00 heroku[web.1]: Process exited with status 127
2014-06-05T17:21:26.879152+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=neuberfranlights.herokuapp.com request_id=f8d51e7a-36ef-4f8c-9988-7cd3e0e67d0a fwd="172.23.21.196, 186.215.116.36" dyno= connect= service= status=503 bytes=
2014-06-05T17:21:27.384852+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=neuberfranlights.herokuapp.com request_id=01e2d601-5cb9-40cd-8e07-fe9c66470adc fwd="172.23.21.196, 186.215.116.36" dyno= connect= service= status=503 bytes=
root@coder:/backup#

As a basis for creating

"var port = Number (process.env.PORT || 5001); app.listen (port, function () { console.log ("Listening on" + port); } ""

I used these two topics:

p>

link

Gypsy,

This is Procfile

(web: tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=$PORT --tilePort=$PORT --tiles=./tiles)

According to this site: link

where you get the Procfile. I figured tilestream would not influence anything at the end of deploy

This guy is the "mentor" of the project:

link

I would be really grateful if you would help me carry it through.

node.js websocket heroku

asked by anonymous 05.06.2014 / 17:35

1 answer

Change a textbox inside a textbox / jQuery group How to make a function return result just after click?

score 1 · Answer 1

The deploy occurred without errors. I tried to enter your site and I had the following screen:

Toviewtheerrorlogs,use:

herokulogs

Thereare more additional options here .

EDIT

Again, the mistake is clear. In the line

Starting process with command 'tilestream --host neuberfranlights.herokuapp.com --host '*' --uiPort=51353 --tilePort=51353 --tiles=./tiles'

Heroku tries to call a command called tilestream and raises the following error:

bash: tilestream: command not found

I do not know what this tilestream is, but it's something your application needs. I can continue to help if I have more information about this project.