We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Besides just not being the New Hotness, using the Bamboo stack limits us to using ruby 1.8.7 or 1.9.2: https://devcenter.heroku.com/articles/bamboo
Unfortunately it looks like a heroku app owner will have to do this and it sounds like somewhat of a tedious, manual process: https://devcenter.heroku.com/articles/cedar-migration
There seems to be some stuff a non-owner can do though, judging from the migration doc above.
The text was updated successfully, but these errors were encountered:
On Mar 12, 2014, at 17:03, pete higgins notifications@github.com wrote:
it's horrible
Sorry, something went wrong.
Merge pull request #75 from phiggins/cedar
1aed6f6
Migrate to Cedar stack (#39)
No branches or pull requests
Besides just not being the New Hotness, using the Bamboo stack limits us to using ruby 1.8.7 or 1.9.2: https://devcenter.heroku.com/articles/bamboo
Unfortunately it looks like a heroku app owner will have to do this and it sounds like somewhat of a tedious, manual process: https://devcenter.heroku.com/articles/cedar-migration
There seems to be some stuff a non-owner can do though, judging from the migration doc above.
The text was updated successfully, but these errors were encountered: