推送后,heroku应用程序仍引用旧文件 [英] heroku application still referencing old files after push

查看:98
本文介绍了推送后,heroku应用程序仍引用旧文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近在Heroku中遇到了这个非常奇怪的问题.

I've been experiencing this very odd problem lately in Heroku.

我在本地进行开发和测试,然后将更改推送到Heroku.即使推送的文件已更改(并且Heroku能够识别并推送新文件),当我在Heroku上查看确切的网页时,它的行为似乎仍在使用我刚推送的文件的旧版本.

I develop and test locally, then I push the changes to Heroku. Even though the files pushed have been changed (and Heroku does recognize it and push the new files), when I look at the exact webpage on Heroku, it behaves as though it was still using the old version of the file that I just pushed.

当我在Firebug中看到HTML源代码时,实际上可以确认正在使用旧文件. 我已经尝试过使用git push -f来强制" git推送,但是没有运气

When I see the HTML source in firebug, I can actually confirm that the old file is being used. I've tried using git push -f to "force" the git push, but no luck

任何想法?

推荐答案

尝试使用heroku restart强制重新启动所有测功.我不是很积极,但是我已经看到类似的迹象,他们倾向于在推动之后懒惰地重新启动"测功机和工人.如果要保证所有工作程序和dynos都在处理最新的推送代码,请在推送后重新启动.

Try heroku restart to force a restart of all the dynos. I'm not positive but I've seen indications like this that they tend to "lazy restart" the dynos and workers after a push. If you want to guarantee all workers and dynos are working off the latest pushed code, do a restart after your push.

这篇关于推送后,heroku应用程序仍引用旧文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆