deploy to heroku without troubless

[atherdon]

2019-02-05T03:34:02.691387+00:00 app[web.1]: We are live on 8004
2019-02-05T03:35:00.424901+00:00 heroku[web.1]: State changed from starting to c
rashed
2019-02-05T03:40:59.804905+00:00 heroku[router]: at=error code=H10 desc="App cra
shed" method=GET path="/routes" host=grocerylists-fake-api.herokuapp.com request
_id=19d28963-b21b-4e4f-875d-be77b201a75a fwd="178.151.41.119" dyno= connect= ser
vice= status=503 bytes= protocol=https

2019-02-05T03:42:22.985162+00:00 heroku[router]: at=error code=H10 desc="App cra
shed" method=GET path="/hello" host=grocerylists-fake-api.herokuapp.com request_
id=04a1ac34-3911-4b9d-bd1e-361d1e99b595 fwd="178.151.41.119" dyno= connect= serv
ice= status=503 bytes= protocol=https

2019-02-05T03:44:23.642317+00:00 heroku[router]: at=error code=H10 desc="App cra
shed" method=GET path="/status" host=grocerylists-fake-api.herokuapp.com request
_id=4219f55a-c7d2-46ca-b8f1-d3a7364b2e94 fwd="178.151.41.119" dyno= connect= ser
vice= status=503 bytes= protocol=https

2019-02-05T03:44:25.408757+00:00 heroku[router]: at=error code=H10 desc="App cra
shed" method=GET path="/favicon.ico" host=grocerylists-fake-api.herokuapp.com re
quest_id=7a7255fb-3aac-4fd7-bc3a-923f046d0238 fwd="178.151.41.119" dyno= connect
= service= status=503 bytes= protocol=https

this is an error log from heroku server. for some reasons it didn't work pretty well

[vadim9999]

where can I find 100% working code on heroku?

[atherdon]

you mean fake-api deployed at heroku?
or you need access to settings at heroku account?
URL saved in description of this repository

[vadim9999]

I will try to deploy to my heroku account this https://medium.com/@grantspilsbury/build-and-deploy-a-node-express-server-to-heroku-in-10-steps-70c936ab15dc simple code.

[atherdon]

I can just add you as a collaborator. or i'm ok that you will try on your own. i think there is not something "big" happens. I think the latest version of express is just required some additional tuning. and it's not about our server setup or our heroku configuration

[atherdon]

it's also not pressing issue for now. i mean if you can run server locally - it can wait

[atherdon]

this article didn't make any different steps also

[vadim9999]

I fixed it

[vadim9999]

You can see it in my deploy on heroku https://rocky-island-20527.herokuapp.com/hello

[atherdon]

i see it on PR build page ;) looks cool. merging. can you also apply the same changes at graphql-server?

[atherdon]

btw, did you add any custom settings to heroku? i mean i deploy it automatically from github repo(lazy variant)

…

On Tue, Feb 5, 2019 at 9:07 PM Arthur Tkachenko < ***@***.***> wrote: i see it on PR build page ;) looks cool. merging. can you also apply the same changes at graphql-server?

[vadim9999]

I doesn't change any parameters in heroku It's problem was in server port and ip in server.js

[vadim9999]

Do you mean deploy graphql to heroku?

[atherdon]

no, i mean you made some changes, and tests start to work. i assume code in the last 3 commits that you've made at tests we calling an url and it return a basic value - telling us that server is not dead. and at graphql we have a same expressjs setup, so it wouldn't be a problem for you.