Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Heroku “No app specified”

DZone's Guide to

Heroku “No app specified”

A super-quick fix for anyone with multiple Heroku apps.

· Cloud Zone
Free Resource

Are you joining the containers revolution? Start leveraging container management using Platform9's ultimate guide to Kubernetes deployment.

I've been having a maddening problem where one (but only one) of my Heroku apps doesn't know which Heroku app it is, which means I need to append --app app-name to every single command. It seemed to happen when I moved my app to an organisation rather than having it on my personal account, but in fact the problem was that at the same time I moved the app I set up the build server to deploy it - and so I removed the old Heroku Git remote and then never added the new one because I exactly shouldn't be pushing to Heroku from my laptop as we now deploy via Jenkins.

I was looking for some config file or something that Heroku would read, but what it actually does is look at whether any of your Git remotes are Heroku - and if so, assume by default that you mean that project! The git URL is on the "Settings" screen from the Heroku web interface, and you just need to add it as a remote to your local project:

git remote add heroku [paste git url from settings screen]

Hopefully this helps someone else stop having to type --app app-name every time they need to do something with their app. It was a tiny problem but quite an annoying one!

Using Containers? Read our Kubernetes Comparison eBook to learn the positives and negatives of Kubernetes, Mesos, Docker Swarm and EC2 Container Services.

Topics:
heroku

Published at DZone with permission of Lorna Mitchell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}