Closed mudetroit closed 9 years ago
@mudetroit Tried to run with DEBUG=* gulp
? It binds to localhost
by default.
Hi @vohof , I am having similar issue, this is the log
tinylr:server param files +520ms { files: [ '/Users/James/work/slide/build/game.css' ] } undefined undefined [ '/Users/James/work/slide/build/game.css' ]
tinylr:server Changed event (Files: /Users/James/work/slide/build/game.css) +2ms
[09:28:05] Finished 'css' after 499 ms
[09:28:05] Starting 'default'...
[09:28:05] Finished 'default' after 7.34 μs
tinylr:server param files +2s { files: [ '/Users/James/work/slide/build/game.js' ] } undefined undefined [ '/Users/James/work/slide/build/game.js' ]
tinylr:server Changed event (Files: /Users/James/work/slide/build/game.js) +1ms
@jamesdam it looks like it notifying about changed files just fine based on that. Are you using the chrome extension?
@vohof , Yes, I am using the latest version of the chrome extension. It was working fine until a few day ago.
This is the console log from the extension:
When I do a curl localhost:35729
I get this
{"tinylr":"Welcome","version":"0.1.4"}
Update: It turns out that there are some problem with my new proxy settings. Thanks for your help, @vohof !
P/S: I am not closing this issue as It was not opened by me.
@jamesdam Good for you!
@volof I ran the command you asked and it does appear to be starting, not sure why nmap was not picking it up.
Looking at the configuration it appears that I need to configure the server option. Two quick questions, what is an expected input (ip address?), and then what call is that passed into which call(listen?).
what is an expected input (ip address?)
If the hostname is omitted, the server will accept connections directed to any IPv4 address (INADDR_ANY). It was listening to localhost
on earlier but I undid that.
what call is that passed into which call(listen?)
https://github.com/mklabs/tiny-lr/blob/master/lib/server.js#L48 https://github.com/vohof/gulp-livereload/blob/master/index.js#L33 https://github.com/mklabs/tiny-lr/blob/master/lib/server.js#L146 https://github.com/mklabs/tiny-lr/blob/master/lib/server.js#L154
Which version are you using?
@vohol Thanks for the help. Apparently being overtired I somehow got server instead of host. What corrected seemed to get it fixed. I did notice that it did still seem to be attaching to the loopback interface.
sudo netstat -tunlp | grep 35729
tcp 0 0 127.0.0.1:35729 0.0.0.0:* LISTEN 6040/gulp
I am using the basic syntax given, but when I attempt to connect to the livereload server it says that it is not running, and nmap seems to confirm this.