-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heroku push rejected, no Cedar-supported app detected #6
Comments
Sorry about that. I merged in some changes from the upstream Ruby On Tue, Mar 19, 2013 at 9:38 PM, Alex Ghiculescu
|
Gemfile:
Gemfile.lock:
|
I just undid the most recent changes on the buildpack. Can you try your deploy again? Sorry for the problems. I'll do more testing next time. |
No worries. Thanks for your prompt help, I really appreciate it :) That seems to have fixed it. Do you think I should report it to the Heroku guys? I don't know very much about buildpacks so I'm not sure what went wrong :/ For the record, I'm trying to deploy this repo: https://github.com/ghiculescu/payaus-docs |
I get the same error. Did you guys find a solution? Thanks. |
I had the same error, then I added a source 'https://rubygems.org'
ruby '2.1.2'
gem 'redcarpet'
gem 'jekyll' Now when I
I don't know where to look in the code, but I would be happy to help fix this issue. |
Same with you @ssaunier . If any ruby version specified in I got another error because the ruby version not specified:
and another error after specified ruby as
No idea how to fix this. Please help. |
Any repo with a I have updated the buildpack with the latest upstream Heroku Ruby buildpack and the current jekyll subcommands. I'm closing this issue, but please feel free to open a new one if you have further problems. |
I'm seeing this output when I try to push to Heroku today. (I wasn't getting this problem last time I pushed, about three days ago.)
My
heroku:config
includes this line:If I remove that (
heroku config:remove BUILDPACK_URL
), I can push with no issues. So I suspect it's something to do with the changes made in the last few days - though looking over them, I'm not sure what it could be. Any ideas?The text was updated successfully, but these errors were encountered: