-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is any additional Setup needed to run JS Tutor? #1
Comments
Hey! I used to have problem deploying on Amazon as well :-( It was because the debugger took sometimes to initialize before it can be used, but the code may send messages to it earlier than that -- and caused it to fail. I tried but I couldn't solve it completely. Have you tried to deploy locally? Does it work locally? |
Yes, it works locally. Weird, I thought EC2 was just like any Linux instance. What server does it work it on? Thanks! |
I'm not sure. Maybe you could try deploying on Heroku (although I believe But I'm not maintaining this project any more. Sorry. You are free to use On Mon, Mar 10, 2014 at 8:31 PM, Ariel notifications@github.com wrote:
|
Yes, it works on Heroku and was much easier to setup! I just had to change the package.json file to |
Last question - how does it capture |
It listens to changes in user program's output stream. It's not just https://github.com/manhhung741/jstutor/blob/master/SourceExecution.js |
I installed this code on Amazon EC2 (along with Node and NPM) and opened port 5858 and 8080. I ran
node server.js
and got the following terminal message:I then visited mysite:8080 which loaded normally. However, when I click on "Visualize Execution" nothing happens in the browser. The terminal displays a message
[SourceExecution] : StdErr Debugger listening on port 6060
.Opening up port 6060 doesn't solve the problem. When I close the server in the terminal, I get a message in the browser "Server error (possibly due to memory/resource overload)..."
Is any additional setup needed to get the Javascript Debugger to work?
The text was updated successfully, but these errors were encountered: