I have a problems using Heroku CLI.
1. I installed Heroku CLI on Winows 10 with all environment variables.
But have this message : "Heroku login the system cannot find the path specified".
What to do to fix it.
I don't know if you are still looking for a solution but I encountered with the same problem today and solved it by doing:
This error was caused by some kind of bug in heroku which prompts uploading heroku.
Everytime I type heroku in the command line. So, I just uninstall and installed the heroku again. However, it kept throwing same error when i type anything start with heroku
The solution was to delete heroku files from:
C:\Users\username\AppData\Local\heroku\cli\bin (%LOCALAPPDATA%\heroku\cli\bin)
Then, when i started it again and it worked smoothly
Related
Hello i am not really sure how to explain my problem or how to ask for help.
But am going to try it anyway lately when i create a react app it installs like normal.
But from the moment i use npm start i get this error (npm start error terminal).
Which says it has nothing wrong with node js/npm so i suspected it was something about the react app dependency that was wrong. When i downgrade to a older version of react scripts it works but the newest version 16.13.1 doesn't work even tho i use this version of react on my windows laptop. In case it helps to solve my issue here is the error log that npm generates (error log npm) i hope this helps to solve my issue
I have found the solution for my problem by setting the path value for system32.
You can do this by the following steps
Goto > Control Panel\System and Security\System\Advance system setting\Enviroment variable and set system variables path C:\Windows\System32\ variable and restart your System.
After i have done these steps it seems to work
This just started happening out of no-where. Did this happen to anybody else? I ran heroku create app and got this error ! error getting commands pid 29989 SIGSEGV (signal 11). This error provides absolutely no information. I use heroku all the time and could not figure why this error started happening. I ran which heroku and it showed heroku files where in /usr/local/heroku/bin/heroku. Basically, I had to uninstall heroku and update node.js to get it working again. Steps I took to get heroku commands to work again.
I updated node.js to version 8.11.1
I unistalled heroku sudo rm -rf /usr/local/heroku
I removed the heroku cache rm -rf ~/.local/share/heroku ~/Library/Caches/heroku
And then installed heroku using the heroku desktop install download.
Even after all that the commands were not working properly, but I started to get a new error of /usr/local/bin/heroku not found. It seems I had to make one more removal to make the commands work again gem uninstall heroku --all and then magically it all started working again.
From what I gathered is my old heroku path was /usr/local/heroku/bin/heroku and the new heroku path is /usr/local/bin/heroku. Perhaps heroku made an update that couldn't find my old path anymore. Best guess.
It sure was a lot to go through to get heroku working again so I thought I should share this for anyone else stuck. And hope if this happens again there could be a better easier solution for this. If there is one please reply.
I used this reference to help walk me through a clean uninstall for mac https://devcenter.heroku.com/articles/heroku-cli#uninstalling-the-heroku-cli
A bit late to this party, but answering in case anyone else encounters the same error. This error is caused by running an outdated distribution of the Heroku CLI (formerly known as the Toolbelt). Uninstalling your current version and re-installing the appropriate distribution from here: https://devcenter.heroku.com/articles/heroku-command-line will do the trick.
I built an application with React/Node.js/PostgreSQL Webpack and now attempting to deploy on heroku.
Everything works perfectly on my localhost, but it doesn't serve on Heroku. error message image on Heroku -
I've tried multiple buildpacks to make it happen, but it still gives me the same result, and I cannot figure out the problem as my logs don't seem to have any issues.
Any ideas would be greatly appreciated.
Here is the link to my repo https://github.com/strongharris/Edu-it
To Run it:
npm install ->
npm run build ->
npm start
The problem here is with your code. I tried to deploy a copy of your project to Heroku, and it's giving me an error because config.connection does not exist when you use it in a conditional.
Here's the error:
(These logs were retrieved by me deploying the Heroku app, then running heroku logs to view the log output.)
As you can see, the error is here: https://github.com/strongharris/Edu-it/blob/master/server/database/database_config.js#L9
You'll need to re-write this code so it runs properly without that variable.
I've been trying to get a Yeoman generated MEAN.js app deployed to Heroku for the best part of a day without much luck.
I've carefully gone through all the steps and am pretty sure I've done everything correctly according to documentation.
After several times going through and ensuring the database is configured correctly with heroku config, removing the public/dist folder from the .gitignore, running grunt build, setting NODE_ENV=production, and running a successful Heroku build the app just continuously shows the very unhelpful Heroku Application Error page.
Upon checking the heroku logs the only thing I can find is this:
bash: ./node_modules/.bin/forever: No such file or directory
Process exited with status 127
Which clearly refers to the Procfile that contains this single line and is where the app is supposed to start from.
web: ./node_modules/.bin/forever -m 5 server.js
There is a server.jsin the root of the project so I tried modifying the Procfile to a standard web: node server.js but that doesn't fix it and I am not comfortable messing with the default Yeoman configuration.
The ./node_modules/.bin/forever is of course there where it is supposed to be. But it obviously isn't showing up or cannot be located in the live Heroku build. If anyone knows what the problem is here and how to fix it I'd much appreciate the help! Cheers!
This happened to me after I upgraded my nodejs, I can't figure out why exactly it is happening, but here is my fix for it asap,
When I ran heroku run ls node_modules/.bin/
I could not find forever there. So I installed and save it to my dependencies by running npm install forever --save
On running heroku run ls node_modules/.bin/ again, it was there and my app runs fine.
I'll sure update this soon, once I figure what exactly led to it.
i am trying to install a node app onto heroku. My application requires both gulp build and gulp install to be called on the server upon instillation, however i am having troubles doing this.
I have tried writing this inside of the package.json:
"scripts":"gulp build && gulp install"
which works at first, but after about an hour the server must restart and recall the script causing for the contents of the server to be rebuilt. this removes all of my content such as newly written blogs or changes.
I have also tried using the heroku toolbelt
heroku run gulp build
heroku run gulp install
However, even though it produces the correct console write lines and looks asif it has made the necessary changes, it hasn't, the server produces an error which proves that the resources haven't been built meaning that the console command didnt make any changes to the actual server files.
Am i missing something out here? Thanks in advance.
So i have figured out that the problem lies with the fact that i have tried to use a LevelDB database on heroku. Apparently, heroku uses no-writable dynos, meaning that the levelDB database is unable to save.