Error deploying to heroku

Question

Please help. I have absoluty no idea what\'s wrong. The rails app works on my local machine.

If I do this:

git push heroku master


        

Answer 1

I was having problems with a repository as small as 130MB. I don't really want to prune my repository, nor do I feel it is necessary.

I can't help but feel this is a problem with git and/or Heroku, I believe a big push should succeed, even over a "slow" or less than ideal connection.

How I solved/worked-around this issue was to spin up an EC2 instance, checkout my repo there, and push to github. In that way, my deploy speed was 4MiB/s (faster than my own 80KiB/s!). Furthermore, in the cases where the push would fail due to some configuration issues, I could quickly tweak and try again.

For more information on this technique, I've written up the full steps on how to spin up an EC2 instance for this purpose here: http://omegadelta.net/2013/06/16/pushing-large-repositories-to-heroku/

Answer 2

I just dealt with 24 hours of this hell. I re-cloned repos, destroyed apps, repacked, pruned... the whole 9 yards.

It turned out that I had a .txt file which was ~250MB in size that, even though I had removed it from my master branch, was still present in my local (as well as github) cache.

I checked out this page and inadvertently found my answer here: https://help.github.com/articles/remove-sensitive-data

The .txt file had previously been in the doc/ folder, so I pointed this command at where the file would have been in any commits and ran it.

git filter-branch --index-filter 'git rm --cached --ignore-unmatch doc/US.txt'

This is very useful if you realize you have static assets of some sort that don't have to be in your repo and are causing you to get the signal 13 error.

Answer 3

Hi I had the same problem trying push to cedar stack. I contacted heroku support and they fixed it. Here is what they said:

It appears to be due to a change in our git server on our end. I'll be following up with our engineers to make sure we get a permanent fix rolled out for this. -Chris

Answer 4

This appears to just be a timeout from your push being too large.

I got around this by doing a git reset to a SHA that was around 500 commits back, pushing that, and then pushing the rest of my repo.