无法推送到 Cedar Stack 上现有的实时 heroku 应用程序 [英] Can't push to existing live heroku app on Cedar Stack

查看:76
本文介绍了无法推送到 Cedar Stack 上现有的实时 heroku 应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

几周前,我在 livebytransit.com 上的 cedar 堆栈上成功地将实时应用推送到 heroku,并且直到最近我还成功地推送了代码更改.从同一工作目录创建临时应用程序后,我无法推送代码更改...请参阅pmn-cloud-6227.herokuapp.com.我的想法是先将更改推送到下午云,然后如果一切看起来不错,就推送到主站点.就目前而言,我无法将更改推送到任一应用程序.

I successfully pushed a live app to heroku on cedar stack at livebytransit.com a few weeks ago, and I have successfully pushed code changes until recently. I have not been able to push code changes after creating a staging app from the same working directory...see afternoon-cloud-6227.herokuapp.com. My thought was to push changes first to afternoon-cloud, then if all looked good, push to the main site. As it stands right now, I can't push changes to either app.

这是一些代码,显示了我尝试过的一些事情.我认为这有很多问题,我最好的办法可能是创建一个新文件夹,从 github 克隆应用程序,然后重新部署到 heroku 上的一个新应用程序并刻录两个现有的应用程序......但我有一些在这个过程中会被吹走的用户,所以如果可能的话,我想挽救我现有目录中的内容.

Here is some code that shows some things I have tried. I think there are so many things wrong with this that my best bet is to probably create a new folder, clone the app from github, and redeploy to a new app on heroku and burn the two existing apps....but I have some users that would get blown away in the process so I would like to salvage what I have in my existing directory if possible.

TBones-MacBook-Pro:livebytransit PG$ git remote -v
afternoon-cloud-6227    git@heroku.com:afternoon-cloud-6227.herokuapp.git (fetch)
afternoon-cloud-6227    git@heroku.com:afternoon-cloud-6227.herokuapp.git (push)
heroku  git@heroku.com:livebytransit.herokuapp.git (fetch)
heroku  git@heroku.com:livebytransit.herokuapp.git (push)
orgin   git@github.com:tom-brown/LiveByTransit.git (fetch)
orgin   git@github.com:tom-brown/LiveByTransit.git (push)

TBones-MacBook-Pro:livebytransit PG$ git add .
TBones-MacBook-Pro:livebytransit PG$ git commit -am"lots of changes that have been pushed to github already via git push orgin master"
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   (commit or discard the untracked or modified content in submodules)
#
#   modified:   voting (modified content)
#
no changes added to commit (use "git add" and/or "git commit -a")

TBones-MacBook-Pro:livebytransit PG$ git push afternoon-cloud-6227

 !  Invalid path.
 !  Syntax is: git@heroku.com:<app>.git where <app> is your app's name.

fatal: The remote end hung up unexpectedly

TBones-MacBook-Pro:livebytransit PG$ git push orgin master
Everything up-to-date

TBones-MacBook-Pro:livebytransit PG$ git remote rm afternoon-cloud-6227
TBones-MacBook-Pro:livebytransit PG$ git remote add livebytransit git@heroku.com:livebytransit.herokuapp.git
TBones-MacBook-Pro:livebytransit PG$ git remote -v
heroku  git@heroku.com:livebytransit.herokuapp.git (fetch)
heroku  git@heroku.com:livebytransit.herokuapp.git (push)
livebytransit   git@heroku.com:livebytransit.herokuapp.git (fetch)
livebytransit   git@heroku.com:livebytransit.herokuapp.git (push)
orgin   git@github.com:tom-brown/LiveByTransit.git (fetch)
orgin   git@github.com:tom-brown/LiveByTransit.git (push)

TBones-MacBook-Pro:livebytransit PG$ git add .
TBones-MacBook-Pro:livebytransit PG$ git commit -a -m "lots of changes already commited to github via git push orgin master"
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   (commit or discard the untracked or modified content in submodules)
#
#   modified:   voting (modified content)
#
no changes added to commit (use "git add" and/or "git commit -a")

TBones-MacBook-Pro:livebytransit PG$ git push orgin master
Everything up-to-date

TBones-MacBook-Pro:livebytransit PG$ git push heroku master

 !  Invalid path.
 !  Syntax is: git@heroku.com:<app>.git where <app> is your app's name.

fatal: The remote end hung up unexpectedly

TBones-MacBook-Pro:livebytransit PG$ git push heroku livebytransit

 !  Invalid path.
 !  Syntax is: git@heroku.com:<app>.git where <app> is your app's name.

fatal: The remote end hung up unexpectedly

TBones-MacBook-Pro:livebytransit PG$ git push heroku git@heroku.com:livebytransit.herokuapp.git

 !  Invalid path.
 !  Syntax is: git@heroku.com:<app>.git where <app> is your app's name.

fatal: The remote end hung up unexpectedly

TBones-MacBook-Pro:livebytransit PG$ git push heroku:livebytransit.herokuapp.git
ssh: Could not resolve hostname heroku: nodename nor servname provided, or not known
fatal: The remote end hung up unexpectedly

让我感到困惑的一件事是为什么 origin 拼写错误.这让我怀疑是不是我不小心改变了这个?任何想法或建议将不胜感激.

One thing that is really puzzling me is why origin is misspelled. It makes me wonder if I somehow changed this by accident? Any thoughts or advice would be very much appreciated.

推荐答案

在我看来,你的 heroku 遥控器好像在 .git/config 中.

It sounds to me like your heroku remote is borked in .git/config.

鉴于您的应用程序位于 livebytransit.herokuapp.com,您的 heroku 遥控器应该是:

Given that your application is living at livebytransit.herokuapp.com, your heroku remote should be:

git@heroku.com:livebytransit.git

如果您希望在两个单独的 Heroku 应用程序中运行同一应用程序的主题分支,我建议您阅读以下内容:

If you're looking to have topic branches of the same application running in two seperate Heroku applications I recommend you read this:

http://neilmiddleton.com/deploying-topic-branches-to-heroku/

这篇关于无法推送到 Cedar Stack 上现有的实时 heroku 应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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