I just installed the latest Heroku Toolbelt (3.1.0) on my Windows 7/64 PC.
I opened a new Command Line and typed 'heroku login'. I get the following error:
C:\Users\Frédéric>heroku login
C:/Program Files (x86)/Heroku/lib/heroku/updater.rb:164:in `spawn': No such file or directory - open (Errno::ENOENT)
from C:/Program Files (x86)/Heroku/lib/heroku/updater.rb:164:in `background_update!'
from C:/Program Files (x86)/Heroku/lib/heroku/updater.rb:144:in `inject_libpath'
from C:/Program Files (x86)/Heroku/bin/heroku:24:in `<main>'
I'm stuck right at the first command :(
Can anyone help ?
If you installed the CLI with apt , you must use sudo apt-get update && sudo apt-get upgrade heroku . If you installed the CLI with npm or yarn , you must use npm upgrade -g heroku or yarn global upgrade heroku .
Maximize your free platform services Get 1000 free dyno hours by verifying your Heroku account with a credit card; unverified accounts receive 550 free hours. You will not be charged, unless you decide to use a paid service.
Scheduler is a free add-on for running jobs on your app at scheduled time intervals, much like cron in a traditional server environment. While Scheduler is a free add-on, it executes scheduled jobs via one-off dynos that will count towards your monthly usage.
1) Open the updater.rb file from ur editor (sublime text 2 here)
2) Remove line 144, which is "background_update!".
After that I simpled typed "heroku login" and it worked.
I had the same problem, which I resolved by adding my own brutal update... i deleted the problem from the source and it actually works fine ! :D
I faced the same issue trying to port my code from Win7 to Win8, which caused me to reinstall pretty much everything, and I couldn't get heroku working. Here's what i did :
1°) Open the updater.rb file from ur editor (sublime text 2 here) 2°) Remove line 144, which is " inject_libpath! " if I recall correctly. 3°) I also removed what's in the else statement, line 164. Thought that wasn't sufficient, it only worked after I deleted line 144. Maybe that's where the real problem comes from.
Anyway, after that I simpled typed "heroku" and it magicaly...worked.
By the way, I also had a problem typing heroku keys:add, which I fixed by creating my own key from the Git Batch Promptcommand, following this :
https://help.github.com/articles/generating-ssh-keys
and then the heroku keys:add command worked perfectly and I could git push heroku master again !
Good luck with Windows8.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With