I can not put a project on heroku.
Constantly writes:

git push heroku master Counting objects: 84, done. Delta compression using up to 8 threads. Compressing objects: 100% (73/73), done. Writing objects: 100% (84/84), 20.44 KiB | 0 bytes/s, done. Total 84 (delta 11), reused 0 (delta 0) remote: Compressing source files... done. remote: Building source: remote: remote: -----> Failed to detect set buildpack https://codon- buildpacks.s3.amazonaws.com/buildpacks/heroku/ruby.tgz remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure remote: remote: ! Push failed remote: Verifying deploy... remote: remote: ! Push rejected to alwizo. remote: To https://git.heroku.com/alwizo.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://git.heroku.com/alw.git'

All the necessary files in the project is. Buildpacks are installed.
I do not understand what he lacks.
If anyone encountered this problem, write how it was solved.
Project on ruby ​​on rails.
Thank!

Closed due to the fact that off-topic participants D-side , Grundy , Abyx , Alex , Alexey Shimansky 14 Dec '16 at 19:55 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • "The question is caused by a problem that is no longer reproduced or typed . Although similar questions may be relevant on this site, solving this question is unlikely to help future visitors. You can usually avoid similar questions by writing and researching a minimum program to reproduce the problem before publishing the question. " - D-side, Grundy, Abyx, Alex, Alexey Shimansky
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • All the necessary files in the project is. - and unlikely. Attach a list of what you have in the root of the repository. - D-side
  • Sorry, that did not immediately respond. I wrote heroku support and literally right after that, it all worked. Even the answer has not yet come from them. So most likely the problem was on their side. - alwizo
  • Interesting. Okay, not playing, not playing like that. - D-side

0