No such file or directory error when starting node server
mannyhenri opened this issue · 8 comments
I right click the directory in sublime, then did LS which as you've seen seem to be in the right directory.
I can't start the node server by the usual commands for this specific project.And yet it works well in terminal shell. Any ideas?
will you show me the result of these environment variables from inside Glue?
echo $SHELL
echo $PWD
█ [ /Users/manny/Sites/Code Samples/GITHUB/eddy ] pwd
/Users/manny/Sites/Code Samples/GITHUB/eddy
█ [ /Users/manny/Sites/Code Samples/GITHUB/eddy ] echo $SHELL
/bin/bash
█ [ /Users/manny/Sites/Code Samples/GITHUB/eddy ] echo $PWD
/Users/manny/Sites/Code Samples/GITHUB/eddy
From: Chris Simpkins
Reply-To: chrissimpkins/glue
Date: Thursday, February 19, 2015 at 12:49 PM
To: chrissimpkins/glue
Cc: Manny Henri
Subject: Re: [glue] No such file or directory error when starting node
server (#32)
will you show me the result of these environment variables from inside
Glue?
echo $SHELL
echo $PWD
—
Reply to this email directly or view it on GitHub.
The glue command pwd matches the actual present working directory in the shell that is spawned to run the command. Your node.js based apps should have access to any of the files in the working directory.
That looks like an exception from your shell environment. It looks like node is not on the system PATH available to the shell spawned by Glue. Glue attempts to read your PATH settings but in some circumstances they aren't correct. Can you confirm whether this is the case? (Link to docs info on Glue paths).
Here is how you modify the Glue PATH if that seems to be the problem.
Let me know if that helps. -C
any luck with this?
Not yet
Thanks
Manny
On Sat, Feb 21, 2015 at 2:09 PM -0800, "Chris Simpkins" notifications@github.com wrote:
any luck with this?
—
Reply to this email directly or view it on GitHub.
thanks Manny. Let me know when you have the chance to try it. -C
@chrissimpkins I haven't been able to answer since I've moved to using Webstorm now. Last I checked the issue was resolved (before the switch).
OK thanks!