git push heroku master需要永远
[英]git push heroku master takes forever
问题描述
I'm using a VM based on Ubuntu 12.04 (ruby 1.9.2p290 and rails 3.1.0) and my app work perfectly on local. 
我正在使用基于Ubuntu 12.04（红宝石1.9.2p290和rails 3.1.0）的VM，我的应用程序在本地完美运行。 I'm using git and when I try to git push heroku master it doesn't work: 我正在使用git，当我尝试git push heroku master它不起作用：
git push heroku master
I get: "Counting objects: 435, done. Compressing objects: 100% (215/215), done. Writing objects: 100% (435/435), 73.35 KiB, done. Total 435 (delta 171), reused 435 (delta 171) " 我得到：“计数对象：435，完成。压缩对象：100％（215/215），完成。写入对象：100％（435/435），73.35 KiB，完成。总计435（delta 171），重用435（ delta 171）“
And it never finish, so it doesn't push anything to heroku. 而且它永远不会完成，因此它不会将任何内容推送到heroku。 The terminal standby forever. 终端永远待命。 I'm new to heroku and git sorry if the question was obvious :) 如果问题很明显，我是heroku和git的新手:)
Operative System information: 操作系统信息：
jobs [1]+ Running git push heroku master &
ps -x
PID TTY STAT TIME COMMAND
1078 ?
1135 ?
1147 ?
1154 ?
1162 ?
1167 ?
1171 ?
1172 ?
1246 ?
1250 ?
1329 ?
1334 ?
1401 ?
1417 ?
1421 ?
1426 ?
1427 ?
1430 ?
1447 ?
1450 ?
1453 ?
1455 ?
1457 ?
1468 ?
1482 ?
1500 ?
1504 ?
1518 ?
1521 ?
1523 ?
1539 ?
1541 ?
1543 ?
1545 ?
1547 ?
1549 ?
1574 ?
1591 ?
1597 ?
1603 ?
1609 ?
1620 ?
1622 ?
1624 ?
1626 ?
1653 ?
1661 ?
1668 ?
1672 ?
1676 ?
1682 ?
1701 ?
1703 ?
1728 ?
1734 ?
1738 pts/2 Ss 0:00 bash
1796 ?
1954 pts/2 S 0:00 git push heroku master
1955 pts/2 S 0:00 ssh git@heroku.com git-receive-pack 'polar-island-471
1959 pts/2 R+ 0:00 ps -x
2 个解决方案
解决方案1
6 2013-08-19 10:20:43
There are many reasons why your push to Heroku can timeout. 推送到Heroku可以超时的原因有很多。 In my experience, the most common reason is due to site size, and by site size, I mean 3 things: the size of your git repo, the size of your site that gets pushed to Heroku (git repo - ignored files), and the size of the gems you use. 根据我的经验，最常见的原因是由于网站大小和网站大小，我的意思是3件事：你的git仓库的大小，你的网站大小被推送到Heroku（git repo - 被忽略的文件），以及您使用的宝石的大小。 Heroku is not particularly robust when it comes to accommodating big sites (or long running processes, for that matter) and if you get too big, you can cause your push to hang / timeout and intermittently too, which can be perplexing. Heroku在容纳大型站点（或者长时间运行的进程）方面并不是特别强大，如果你变得太大，你可能会导致你的推送暂停/超时和间歇性，这可能是令人困惑的。
.git folder I have had the site get unexplainably large and saw that over time my .git folder in the root of the project had grown to 600mb. .git文件夹我让网站变得无法解释地大，并且随着时间的推移，我看到项目根目录中的.git文件夹已经增长到600mb。 Thank goodness I noticed a warning in the heroku deploy chatter that warned me that my git repo was too large. 谢天谢地，我在heroku部署聊天中注意到一个警告，警告我git repo太大。 Anyway, since that folder is managed by git behind the scenes, I ended up starting a fresh git repo and moving my code over to it, which shrunk my site by 90%. 无论如何，由于该文件夹是由git在后台管理的，所以我最终开始了一个新的git repo并将代码移到该文件夹中，这使我的网站缩小了90％。
.slugignore Another pitfall that caused my site to become large enough to timeout was allowing things like logs, my temp directory, and my solr indexing directory to be included in the project. .slugignore导致我的站点变得足够大以至于超时的另一个陷阱是允许将日志，临时目录和solr索引目录等内容包含在项目中。 After I excluded all of those folders in my .slugignore file, pushing became very fast. 在我的.slugignore文件中排除了所有这些文件夹后，推送变得非常快。 And yes, you could get the same basic effect using .gitignore, but there are some things that I like to manage through git, but ignore when pushing to heroku. 是的，你可以使用.gitignore获得相同的基本效果，但有些东西我喜欢通过git管理，但在推送到heroku时会忽略。 That's when the .slugignore comes in handy. 那时候.slugignore派上用场了。
gems By completing the steps above, I reduced my site to a reasonable size, but still had occasional timeouts. gems通过完成上述步骤，我将网站缩小到合理的大小，但偶尔也会超时。 Then I realized that gems contribute to your site size too. 然后，我意识到宝石也对您的网站规模有所贡献。 So I removed a handful of unused gems from my gemfile, and I was able to reduce my slug compile time from 900+ seconds to 250 seconds and my overall deployment time from 15+ minutes with frequent timeouts to under 10 minutes. 所以我从我的gemfile中删除了一些未使用的宝石，并且我能够将我的slug编译时间从900秒减少到250秒，并且我的总体部署时间从15分钟以上，频繁超时到10分钟以下。 What a relief to not have to wait so long for each deploy and risk timing out half the time. 对于每次部署而言不必等待这么长时间并且冒出一半时间的风险超时，这是多么轻松。
Depending on your particular setup, any or all of these factors can really hurt you. 根据您的特定设置，所有这些因素中的任何一个或全部都可能确实伤害您。 In my case I was doing everything wrong. 就我而言，我做错了一切。 However, even if you are not timing out, you may still want to prune your site as much as possible to cut down your deployment time. 但是，即使您没有超时，您仍可能希望尽可能地修剪您的网站以缩短部署时间。
how to make heroku not suck http://www.stormconsultancy.co.uk/blog/development/6-ways-to-get-more-bang-for-your-heroku-buck-while-making-your-rails-site-super-snappy/ 如何使heroku不吮吸 http://www.stormconsultancy.co.uk/blog/development/6-ways-to-get-more-bang-for-your-heroku-buck-while-making-your-rails-现场超活泼的/
解决方案2
1 已采纳 2016-04-06 15:36:59
The reason was, that my connection was very slow. 原因是，我的连接非常慢。 It was the Access Point of my smartphone. 那是我的智能手机的接入点。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.