Meteor hangs when building the app

[realyze]

Looks like meteor has changed the build process behaviour and now the builds hang.

The problem is that meteor is checking ${HOME}/.meteor to load package metadata (which is empty).

Look at realyze@7f2d560#diff-03bfd081eda3a1e9dc94b17cc19ba246R44 for a possible fix.

[andrejsm]

The fix works. Thanks!

[agarbund]

@realyze you saved my day. Thanks

[sb07]

I get the following loop in the cmd after setting buildpack to realyze fork and git push heroku master

'remote: Adding syncToken:
remote: {"lastDeletion":1409018311766,"format":"1.1","packages":145348149
6375,"versions":1445286051705,"builds":1445292751792,"releaseTracks":14498101501
70,"releaseVersions":1453360852144}
remote: Returning sync token:
remote: {"lastDeletion":1409018311766,"format":"1.1","packages":145348149
6375,"versions":1445286051705,"builds":1445292751792,"releaseTracks":14498101501
70,"releaseVersions":1453360852144}'

It finished and the app has an error. The app runs locally.

[rfines]

There is a different buildpack that can be used to build and deploy your meteor apps to Heroku. I am not affiliated with it, but it did fix the deployment issues that I was having. You can find it here:
https://github.com/AdmitHub/meteor-buildpack-horse

[sb07]

heroku buildpacks:set https://github.com/AdmitHub/meteor-buildpack-horse.git
git push herokumaster

Everything up-to-date
heroku restart
Restarting dynos... done

Application still has error. It deploys to meteor.

[sb07]

This was in the logs:
Jan 22 11:36:25 test2016cart2 heroku/router: at=error code=H10 desc="App crashed" method=GET path="/" host=test2016cart2.herokuapp.com request_id=91487a02-0754-4dd4-ae41-bd0661bc29d2 fwd="75.84.140.123" dyno= connect= service= status=503 bytes=
Jan 22 11:36:25 test2016cart2 heroku/router: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=test2016cart2.herokuapp.com request_id=33abf4df-a0d0-454f-906a-739dd999188a fwd="75.84.140.123" dyno= connect= service= status=503 bytes=

[joegoldbeck]

+1

[sb07]

the horse pack worked for me. MongoURI did not need to be manually set.

I didnt rerun with realyze, obviously it probably works too.

[scheung38]

Could someone expand on the fix, I am using Mac OSX

Symlink .meteor dir to ${HOME}/meteor.

ln -s ? ?

[joegoldbeck]

Just tried the horse pack as well. Doesn't have this issue and builds way
faster, despite the extra installed dependencies (phantomjs).

[scheung38]

Failed to load resource

503 referring to my public/favicon

which are in my public/favicons, but Heroku cannot find it? So if it is not an issue but Heroku cannot find it then not sure how to resolve it?

[agarbund]

realyze fork contains some more work than just commit which is fixing Heroku builds. Until realyze commit is merged I've created my own fork and applied only needed fix on it. Works well for me: https://github.com/agarbund/heroku-buildpack-meteor

[realyze]

@scheung38 ln -s <dir> <target> creates a symbolic link of dir as target. Meteor is looking for some cached package metadata in $HOME/.meteor and if missing it will try to download it (which is super slow). Creating the symbolic link makes sure meteor can find the metadata.

[codebreach]

@agarbund's repo fixed it

[smitev]

@scheung38 I had the same 503 error, it was caused because I had the "/private" folder in my .gitignore file. After I included only "/private/settings.json" there, everything went well.

[gg2001]

I had similar issues, and I wrote an article on how to solve them. Check it out: https://medium.com/@gautham.gg/deploy-a-meteor-1-3-application-to-heroku-cda1f68ca20a#.on7al5t2v