views:

285

answers:

1

When I type: git push heroku master, this is what happens

$:sample_app git push heroku master
Counting objects: 110, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (94/94), done.
Writing objects: 100% (110/110), 87.48 KiB, done.
Total 110 (delta 19), reused 0 (delta 0)

-----> Heroku receiving push
-----> Rails app detected
 !     This version of Rails is only supported on the Bamboo stack
 !     Please migrate your app to Bamboo and push again.
 !     See http://docs.heroku.com/bamboo for more information
 !     Heroku push rejected, incompatible Rails version

error: hooks/pre-receive exited with error code 1
To [email protected]:blazing-frost-89.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '[email protected]:blazing-frost-89.git'

My .gems file:

rails --version 2.3.8

My .git/config file:

[core]
  repositoryformatversion = 0
  filemode = true
  bare = false
  logallrefupdates = true
  ignorecase = true
[remote "origin"]
  url = [email protected]:csmeder/sample_app.git
  fetch = +refs/heads/*:refs/remotes/origin/*
[remote "heroku"]
  url = [email protected]:blazing-frost-89.git
  fetch = +refs/heads/*:refs/remotes/heroku/*
+4  A: 

Like it says, Rails 2.3.8 is only available on their Bamboo stack. I think it's because Bamboo is slated to become the default stack in the near future, and Rails has only been upgraded on that stack.

mipadi
I don't understand. If I use the following commands:185-86-134:sample_app heroku createCreating blazing-frost-89.... doneCreated http://blazing-frost-89.heroku.com/ | [email protected]:blazing-frost-89.gitGit remote heroku added185-86-134:sample_app git push heroku masterYou think it would create itself on the correct stack? I have to create it and then manually migrate it? It seems like something is wrong. Shouldn't it create on Bamboo if it really needs to be on Bamboo.
The Aspen stack is still the default, for the time being. When you create a project on Heroku, it can't know your project requirements (i.e., you may be using an older version of Rails) until you actually push.
mipadi