I opened a heroku account.
I followed the instructions on http://docs.heroku.com/quickstart.
I have a working rails app which I have deployed successfully elsewhere.
I have a github account that works.
I have a local git repository for my rails app.
I installed the heroku gem. It shows up in my gem list.
I typed 'heroku create' at the command prompt...
My command console showed that it was thinking about it, but did nothing. No errors. No action.
Possible related facts: I am using a Windows 7 machine. I have also failed miserably at deploying with capistrano with a similar--issue command, get no response--pattern.
I'm pretty sure now that it's a Windows issue. I don't know what exactly, it could be that the heroku gem doesn't support a Windows environment very well, or it could be something else.
However, since my original post I installed Ubuntu via VirtualBox on the same machine. From that installation I ran heroku create on the same app and it worked as expected.
Related
As of this morning, without having change anything in my Heroku CLI setup, I received the following error when I tried to run:
heroku logs -t -app <app_name>
! Please specify a version along with Heroku's API MIME type. For example, Accept: application/vnd.heroku+json; version=3.
I have since tried updating both heroku and heroku-toolbelt via brew upgrade heroku and brew upgrade heroku-toolbelt, but this did not solve the issue.
I get this error essentially whenever I try to do anything with heroku CLI, including heroku logs, heroku apps, heroku login, and heroku auth:login.
I am running MacOS, and the error posted is the only information that I am getting back from Heroku.
This discussion here: How can I specify heroku's MIME type? pertains to upgrading Heroku in Ubuntu and does not solve my issue.
I had the same problem -- but installing the new Toolbelt did not work at first. There was one other step I needed to do.
from: https://devcenter.heroku.com/articles/heroku-cli
It has instructions for each platform on installing the new cli -- and says you need to run: which heroku in order to verify the proper version is running. In my case I also needed to do a gem uninstall heroku in order to get everything working, as it was running the gem binary instead of the newly installed heroku-cli binary.
If you were using heroko Plugin for intellij
I tried alot to make it work !
From here official response
#emzeidan thanks for the report. This plugin is deprecated, and uses an old version of the Heroku API that has been shut down. Please recommend to your users that they use one of the alternative deployment mechanisms described in our DevCenter article on WAR deployment. If you can remove from the plugin from any Bamboo marketplace (or similar thing) that would be helpful too. Thanks.
This was on Sept-2017
I run the 'heroku --version' command and the toolbelt automatically updates the client. After that the login was ok.
I had the same problem on macOS Sierra 10.12.3 when I installed heroku via brew.
To get round it I ran brew uninstall heroku-toolbelt then installed via the Mac installer at https://devcenter.heroku.com/articles/heroku-cli#macos and it works fine now.
Have you specified the heroku gem in your Gemfile? If yes, then remove it.
And then, install Heroku CLI for https://devcenter.heroku.com/articles/getting-started-with-ruby#set-up and run your command.
When I try to use heroku pg:psql, the following error is displayed.
! This version of the API has been Sunset.
! Please see https://devcenter.heroku.com/changelog-items/1147 for more information.
How can I access postgresql on Heroku?
heroku pg:psql command worked a few week ago.
I develop my Rails app on the Cloud 9.
I had the same issue with my ruby on rails project since last Friday.
However, i was able to resolve this error message by update my heroku toolbelt on my mac os.
*Hint, if your heroku file was installed in project gem. you will need to delete that file.
Use command which heroku to identify where is the heroku file. if it is inside the .rvm folder that means your project is still using outdated heroku file. and simply remove it and then ran an new install heroku cli should fix this error.
Let me know if this works for you.
I'm working against a variety of constraints that are troubling an EC2 Rails deployment. I'm not allowed to use Capistrano because I cannot save this application to any public git repository (like GitHub) and I also need to retain complete control over which instance on EC2 the Rails application is installed to and be able to modify this easily (adding load balancers, auto-scalers, etc.) on the fly from the AWS Console, so I also cannot use Rubber.
I finally resorted to simply ssh'ing my Rails application directory over to the EC2 instance, but am running into a 'no such file to load' error when running bundle install, specifically the Time gem. Because this is an 'integrated' gem, I think I might just be overlooking something simple. Here are the things that I've tried:
I've used RVM to manage my versions of ruby, rails, rubygems, etc.
Deleting my Gemfile.lock file and re-running bundle-install
Including 'Time' in my GemFile and re-running bundle-install
This application runs without issue on my local development environment, so what am I overlooking?
Note: I am REQUIRED to host on a single EC2 instance. Otherwise, I'd simply deploy to EBS, Heroku, etc.
This was a stupid mistake, also detailed in this question: heroku - cant run rake db:migrate - no such file --Time
I incorrectly had a require statement in a controller for 'Time', instead of 'time'. This was allowed locally, but my ubuntu server ruby environment was not as forgiving. Changing the 'T' to a 't' in my controller and running 'bundle install' resolved this issue completely.
I updated a gem(rtf) in my ruby on rails app through the Gemfile. The app works fine on my localhost but when I pushed changes to heroku and tried 'bundle install' within heroku bash. I see that the gem has been installed based on the log
Using rtf (0.3.3)
Following this, I did a
heroku restart --a myapp
however, when i tried the app on heroku, it still cant recognize the lib installed through the gem, i get the following error(normally appears when the library cannot be reached for command "require 'RTF'").
cannot load such file -- RTF
What am I doing wrong in heroku?
I think you misunderstand how Heroku works. When you run a bash shell on your app, nothing you do on that dyno will affect any other dynos for your app (like your web dynos). Heroku runs bundle install for you when you deploy your app and if your Gemfile is configured correctly all the gems will be installed.
the answer by sevenseacat is right- i had just got the case wrong-
require 'rtf'
works fine. In OSX, it ignores case in the command require 'RTF'
I downloaded the windows version of heroku toolbelt from here https://toolbelt.heroku.com/
I chose my folder as
C:\Program Files (x86)\Heroku
which is NOT where my rails app directories are.
Now, according to the heroku homepage guide, https://devcenter.heroku.com/articles/quickstart#step-2-install-the-heroku-toolbelt
it says
"Step 3: Login
After installing the Toolbelt, you’ll have access to the heroku command from your command shell. Authenticate using the email address and password you used when creating your Heroku account:"
Where do i go to do this? I don't see an executable command terminal file in any of the folders of where Heroku installed itself.
My heroku folder contains these directories and files
bin
data
lib
ruby-1.9.2
vendor
unins000.dat
unins000.exe
unins000.msg
I try to execute commands on my windows command prompt, but that doesn't work either. I also used railsinstaller to install rails, ruby, git, etc., so i tried to run heroku commands from the Git Bash and that does not work either.
All of the instructions i read online, including the Github page for heroku toolbelt omits this crucial information. https://github.com/heroku/heroku.rb They will all tell you what commands to type, but don't tell you where to go or which command terminal to open from which folder after downloading.
Now, from my Git bash terminal, which I got from using railsinstaller, I can install the heroku gem, foreman gem, but the heroku gem is deprecated. Toolbelt is what I should be using, and here I am without a critical piece of information.
Does no one else have any problems installing heroku toolbelt and getting it to function? I'm kind of surprised that the omitted information hasn't seemed to spark other heroku toolbelt installation questions yet. Hopefully this question will help other first-timers as well.
Thank you in advance.
You need to be logged in as an administrator for the installation to work. If you weren't try it again with that privilege.
After installing the toolbelt, the system path should include the installation folder's bin. On my 64-bit Win 7 box its':
C:\Program Files (x86)\Heroku\bin
There should also be a system level variable called HerokuPath.
So if you start a new CMD shell, say path and what appears should include the path above (or similar for your machine).
Also say set HerokuPath and the path should appear here.
Then the heroku command should run with no problems, and you can follow the instructions.
If you still have problems, it's likely that one of the embedded installations in the toolbelt is in conflict with another version of the same already on your system. Try running a shell that has a minimal path plus the HerokuPath contents. The most likely culprit is another Ruby installation. The heroku command is a Ruby script in disguise.