I tried it out today with the latest NodeJS, and found I was getting
the same. I suspect that the internal path mechanism for identifying
the current directory changed in the new NodeJS.
I pushed a fix to the gitorious repository to fix this.
Let me know if you have any other problems, and feedback is always good.
Ta
Jamie
--
Jamie Love
Looking for custom software development? Contact us at www.nsquaredsoftware.com.
Thanks for your patience -
I've committed and pushed to the public repository a change that I
hope (this time!) will fix your problem.
The deploy directory was built using a set of soft links, and while
useful for rapid development, isn't actually great for deploying.
I've adjusted it to copy files into the deploy directory, which
hopefully will solve the problem on your system. After updating the
software code, please run (in the root directory of R-Node):
make clean
make
this'll rebuild the deployment directory.
If the server still doesn't run, please copy/paste the output in as
you've been doing - it is helpful.
Thanks
Jamie Love
Strange things afoot - I copied the gitorious codebase anew, and it
started failing for me, despite there being absolutely no differences.
I've made a change to the code to try and fix it in a different way,
essentially by defining the complete path to the file in question,
rather than relying on nodejs's module lookup code - please try again.
Ta
Jamie
Excellent to hear.
If you have any further problems or questions please ask.
Jamie
On 17/02/2011 2:57 AM, "Brian Weiner" <weiner...@gmail.com> wrote:
Mission Accomplished!I'm playing with it now... Your help was much appreciated!
Brian
On Wed, Feb 16, 2011 at 5:13 AM, Jamie Love <drj...@gmail.com> wrote:
>
> Hi there,
>
> Strange t...