Heroku push rejected, no Cedar-supported app detected

[davidthewatson]

I'm running on Mac OS X Lion with the latest updates and lib event installed via brew. Everything seems to work fine until I try to deploy, at which point I get the "no Cedar-supported app detected" error, despite the fact that I've done:

heroku create junker --stack cedar

Here's the output from the git push:

(env)Davids-MacBook-Pro:env davidthewatson$ git push heroku master
Warning: Permanently added the RSA host key for IP address '50.19.85.132' to the list of known hosts.
Counting objects: 985, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (925/925), done.
Writing objects: 100% (985/985), 3.94 MiB | 842 KiB/s, done.
Total 985 (delta 57), reused 0 (delta 0)

-----> Heroku receiving push
! Heroku push rejected, no Cedar-supported app detected

To git@heroku.com:junker.git
! [remote rejected] master -> master (pre-receive hook declined)

error: failed to push some refs to 'git@heroku.com:junker.git'

Thanks,
David

[zachwill]

Hmm, that's bizarre — especially since that name's not taken. And I'm assuming all the files are intact, too (bootstrap.py, same app layout, etc)? \ Let me make a quick side app and see if my push fails, too.

[zachwill]

Test app went through. Maybe running a heroku destroy and then going through the steps again should work? And I'm assuming you're using the latest revisions to this repository (so your Procfile and everything should be solid).

I found some tweets from awhile back about some weirdness, but nothing recent — maybe it was a momentary bug with Heroku?

[davidthewatson]

No, it's repeatable even after the destroy. I had done that before I posted this issue. Sorry, should have mentioned that.

Apparently, this started back in August...

mwotton/heroku_haskell_demo#2

but the cause and workaround are not exactly clear to me since I don't know much about the underlying heroku implementation. Anything specific I should check or try?

[zachwill]

If it's open-source, you could push it up to Github and I can take a look at the repository? Interesting bug — definitely don't want anyone else to go through these problems.

[davidthewatson]

I followed the directions from your project landing page on github. I didn't even change the directory name as you can see here:

https://github.com/davidthewatson/env

Let me know if I made a mistake. Thanks!

[zachwill]

Looked through it and it seems the env is 100% right. A quick workaround I can think of is cloning flask_heroku into a new repository, then...

1. rm -rf .git
2. git init && git aa
3. git ci -am "First commit"
4. heroku create --stack cedar
5. git push heroku master

If that goes through, you can port your modified files from junker over — and odds are you'll find the problem.

A slightly involved solution to create a new application, but I'm stumped at the moment. Hope that helps!

[davidthewatson]

I think the problem stemmed from my being in the virtualenv (env) directory when I did the git stuff. It wasn't obvious to me that I should have been in the heroku-flask directory. I did rm -rf on .git in the env directory then went up to the heroku_flask directory and repeated the heroku commands. I now have the app running on heroku so thanks for the help!
I also had to add my pub key to heroku or I got permission denied.

heroku keys:add ~/.ssh/id_rsa.pub

Please confirm that I'm understanding this correctly and it might help to update the readme with the aforementioned.

Cheers,
Dave

[zachwill]

Good deal — glad you got everything worked out, man. I'll close this issue and update the README.