So I am learning how to use git with Heroku and I can't seem to git push my set repo. So I set the buildpack to ruby with Heroku as ruby by doing so..
root#slacker:~/ruby# heroku buildpacks:set heroku/ruby
Buildpack set. Next release on stormy-earth-98069 will use heroku/ruby.
Run git push heroku master to create a new release using this buildpack.
Next I try to update my repo using git push and I get an error saying this..
root#slacker:~/ruby# git push heroku master
...
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
...
So I am wondering what could cause git to do this?
Your question has the answer. According docs, looks like the directory from where you are running 'git push' doesn't have Gemfile.
Related
When I try to deploy the branch in heroku, I get this error:
-----> Building on the Heroku-22 stack
-----> Using buildpack: heroku/python
-----> App not compatible with buildpack: https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/python.tgz
More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
! Push failed
I do have a Procfile and a requirements.txt file in the root directory. Any idea what the issue may be?
I tried deploying my application today and my deployments are for the first time being rejected.
My deployment output is below. I've tried the following with no change in outcome:
Deploying with no Ruby version in Gemfile
Deploying with 2.1.0 in Gemfile
Deploying using a custom BUILDPACK_URL at https://github.com/heroku/heroku-buildpack-ruby.git
Deploying from a different branch
Deploying from a teammate's machine
Rolling back to last successfully deployed commit, changing a line in the README, committed and redeployed.
I had successfully deployed just last night. I only have made HTML and CSS changes to the new code I want to commit, so nothing in the app settings has been changed since the last successful deployment.
Why would Heroku be now rejecting my app deployments?
Thanks!
Fetching repository, done.
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 496 bytes, done.
Total 6 (delta 5), reused 0 (delta 0)
-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.0.0
-----> Installing dependencies using 1.5.2
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
env: bundle: No such file or directory
Bundler Output: env: bundle: No such file or directory
!
! Failed to install gems via Bundler.
!
! Push rejected, failed to compile Ruby app
To git#heroku.com:myapp.git
! [remote rejected] development -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:myapp.git'
Heroku dropped support for Rails 1.9 and that was in the PATH. I had some trouble dropping the PATH because heroku had some hack where it was configured, but would not drop (probably because it was a default).
So I ended up setting the PATH to something
heroku config:set PATH=blah
and then unsetting it.
heroku config:remove PATH
That seems to have stuck.
I've followed all the questions on here already but am STILL getting an error pushing to Heroku.
Here's what I've done so far:
Remove sqlite3 completely from the gemfile, bundle, git commit and git push to Heroku.
Put sqlite3 into group :development, :test do, bundle, git commit and git push to Heroku.
Uninstall and reinstall sqlite3 gem, bundle, git commit and git push to Heroku.
Remove the Gemlock file, bundle, git commit and git push to Heroku.
Gem file:
group :development, :test do
gem 'sqlite3'
end
group :production do
gem 'rails_12factor'
gem 'pg'
end
Git status is clean.
Git push heroku master failure log is here - http://pastebin.com/K2192h8A
Hopefully someone can let me know what I've done wrong. Thank you.
Ended up rebuilding the app and it is now deployed.
Always take care to look and make sure you are under the correct git branch!
if you are using
git push heroku master
then do the command
git branch
and make sure that you are under the master branch and not elsewhere. You are using git to push to heroku so it make not always be your rails app that is causing the problem. Be sure to
git add.
and
git commit -m "comment"
before looking at your rails app for mistakes.
this question solved this for me.
Heroku Push - Error with Git Push to Heroku
next time you buil a new app to get rid of all the fuss you must do the following: rails new -d postgresql ,if u don't have heroku addons installed do this heroku addons:add heroku_postgresql:hobby-dev
next heroku addons | grep POSTGRES and finally heroku run rake db:migrate
that should be it
i am currently trying to deploy an app to heroku
https://github.com/Shopify/dashing/wiki/How-to%3A-Deploy-to-Heroku
I am following these instructions exactly
bundle install
git init
git add .
git commit -m "My beautiful dashboard"
heroku apps:create myapp
git push heroku master
and receive this error everytime
git push heroku master
Counting objects: 441, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (225/225), done.
Writing objects: 100% (441/441), 503.88 KiB | 445 KiB/s, done.
Total 441 (delta 170), reused 441 (delta 170)
-----> Heroku receiving push
-----> Ruby app detected
!
! Gemfile.lock is required. Please run "bundle install" locally
! and commit your Gemfile.lock.
!
! Heroku push rejected, failed to compile Ruby app
you don't have a Gemfile.lock file
try
bundle install and then git commit -am "message you wanna put here"
as mentioned below, check the gitignore and remove /Gemfile.lock and the commit again may resolve your problem
I have a Node project that is using Bundler and Guard to handle my pre-compilations steps.
This means that I have a Gemfile in the root of my project along with the package.json file.
My problem is that Heroku believes that my project is a Ruby app, just because the Gemfile exists. And complains that I have not committed the Gemfile.lock, which I don't want to commit.
-----> Heroku receiving push
-----> Ruby app detected
!
! Gemfile.lock is required. Please run "bundle install" locally
! and commit your Gemfile.lock.
!
! Heroku push rejected, failed to compile Ruby app
Is there a way to tell Heroku that the app is a Node app and not a Ruby app?
The solution to this, with a lot of help from Heroku Support is: use a build pack!
Override the Heroku default buildpacks by specifying a custom buildpack in the BUILDPACK_URL config var
$ heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs
You can also specify a buildpack during app creation
$ heroku create -s cedar --buildpack https://github.com/heroku/heroku-buildpack-nodejs
Simple when you know it. Some more documentation can be found at Heroku Dev Center
It seems there's a new way to do this as BUILDPACK_URL is now deprecated, explained here, but essentially the command is:
$ heroku buildpacks:set heroku/nodejs
You may also specify a buildpack during app creation:
$ heroku create myapp --buildpack heroku/nodejs