starred/whoogle-search

Fork 0

mirror of https://github.com/benbusby/whoogle-search.git synced 2026-04-25 12:15:50 +03:00

[GH-ISSUE #63] [QUESTION] How to update when deployed via Heroku Quick Deploy? #42

New issue

Closed

opened 2026-02-25 20:34:46 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 20:34:46 +03:00

Owner

Originally created by @pred2k on GitHub (May 18, 2020).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/63

It's awesome how easy (and cheap) it is to deploy it to heroku. ❤️
And it works really great since a week.
But now i saw nice changes like https-only and so on and i tried to find out how i update a heroku app.
Found https://blog.heroku.com/six-strategies-deploy-to-heroku where he says:

Cons: Apps deployed via button do not auto-update when new commits are added to the GitHub repo from which it was deployed

Could someone help me here please?
Is heroku cli the way to go? Or can i link my github account to the app for automated updates?

Originally created by @pred2k on GitHub (May 18, 2020). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/63 It's awesome how easy (and cheap) it is to deploy it to heroku. ❤️ And it works really great since a week. But now i saw nice changes like https-only and so on and i tried to find out how i update a heroku app. Found https://blog.heroku.com/six-strategies-deploy-to-heroku where he says: > Cons: Apps deployed via button do not auto-update when new commits are added to the GitHub repo from which it was deployed Could someone help me here please? Is heroku cli the way to go? Or can i link my github account to the app for automated updates?

kerem

2026-02-25 20:34:46 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-25 20:34:46 +03:00

Author

Owner

@pred2k commented on GitHub (May 18, 2020):

I've played around and it looks like following does a deployment of current master to my heroku deployment created via Heroku Quick Deploy:

git clone https://github.com/benbusby/whoogle-search.git
cd whoogle-search
heroku git:remote -a <name_of_my_heroku_app>
git push heroku

and future updates would be:

cd <path_to>/whoogle-search
git pull
git push heroku

What i still need to figure out is, how to deploy release tags only.
From https://devcenter.heroku.com/articles/git#deploying-from-a-branch-besides-master i've tested:

git push heroku v0.1.1:master                                                                                                                                         e3d002f
To https://git.heroku.com/MYAPPP.git
 ! [rejected]        v0.1.1 -> master (non-fast-forward)
error: failed to push some refs to 'https://git.heroku.com/MYAPPP.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

that probably fails because i pushed master before.
Could i do the following after the next release?

git pull
git push heroku v0.1.2:master

@pred2k commented on GitHub (May 18, 2020): I've played around and it looks like following does a deployment of current **master** to my heroku deployment created via Heroku Quick Deploy: ``` git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search heroku git:remote -a <name_of_my_heroku_app> git push heroku ``` and future updates would be: ``` cd <path_to>/whoogle-search git pull git push heroku ``` What i still need to figure out is, how to deploy release tags only. From https://devcenter.heroku.com/articles/git#deploying-from-a-branch-besides-master i've tested: ``` git push heroku v0.1.1:master e3d002f To https://git.heroku.com/MYAPPP.git ! [rejected] v0.1.1 -> master (non-fast-forward) error: failed to push some refs to 'https://git.heroku.com/MYAPPP.git' hint: Updates were rejected because a pushed branch tip is behind its remote hint: counterpart. Check out this branch and integrate the remote changes hint: (e.g. 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. ``` that probably fails because i pushed master before. Could i do the following after the next release? ``` git pull git push heroku v0.1.2:master ```

kerem commented

2026-02-25 20:34:46 +03:00

Author

Owner

@benbusby commented on GitHub (May 19, 2020):

In the error from the second half of your comment, it seems like the only thing it's complaining about is the branch needing remote updates pulled in locally before pushing again (so all that would be needed is a git pull before re-running that push command for v0.1.1). I have a couple heroku instances running, I'll try to test out this method this week sometime and see what I run into.

@benbusby commented on GitHub (May 19, 2020): In the error from the second half of your comment, it seems like the only thing it's complaining about is the branch needing remote updates pulled in locally before pushing again (so all that would be needed is a `git pull` before re-running that push command for `v0.1.1`). I have a couple heroku instances running, I'll try to test out this method this week sometime and see what I run into.

kerem commented

2026-02-25 20:34:46 +03:00

Author

Owner

@pred2k commented on GitHub (May 24, 2020):

Updating to the latest releases works like charm.
Having heroku CLI setup in a repo-clone like i wrote above, this one simply deploys a new release tag:

cd <path_to>/whoogle-search
git pull
git push heroku v0.1.4:master

is the README.md a place for this update steps?

i'm now thinking about an automated deployment way for release tags of a heroku app.
The Heroku github connection only allows automatic deployments on own repos (forks dont have automated sync) and branches only.
https://devcenter.heroku.com/articles/github-integration#automatic-deploys

Is anyone more experienced with the github/heroku connection that can give an hint on that?

@pred2k commented on GitHub (May 24, 2020): Updating to the latest releases works like charm. Having heroku CLI setup in a repo-clone like i wrote above, this one simply deploys a new release tag: ``` cd <path_to>/whoogle-search git pull git push heroku v0.1.4:master ``` is the `README.md` a place for this update steps? ____ i'm now thinking about an automated deployment way for release tags of a heroku app. The Heroku github connection only allows automatic deployments on own repos (forks dont have automated sync) and branches only. https://devcenter.heroku.com/articles/github-integration#automatic-deploys Is anyone more experienced with the github/heroku connection that can give an hint on that?

kerem commented

2026-02-25 20:34:46 +03:00

Author

Owner

@benbusby commented on GitHub (Oct 26, 2020):

I added a wiki page with the contents of this discussion here. I'll look into how Herolku handles automatic deployments and update the wiki if I find anything enlightening.

@benbusby commented on GitHub (Oct 26, 2020): I added a wiki page with the contents of this discussion [here](https://github.com/benbusby/whoogle-search/wiki/Updating-a-Heroku-Quick-Deploy-Instance). I'll look into how Herolku handles automatic deployments and update the wiki if I find anything enlightening.