Open medialwerk opened 8 years ago
You don't have to set that. Remote-atom will work accordingly.
not right imho
$ telnet localhost 52698
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Atom 1.26.1
^]
telnet> q
Connection closed.
$ telnet 192.168.1.127 52698
Trying 192.168.1.127...
telnet: connect to address 192.168.1.127: Connection refused
telnet: Unable to connect to remote host
For now I'm using
ssh -g -L 52697:localhost:52698 -N localhost
or
socat tcp-listen:52697,reuseaddr,fork tcp:localhost:52698
and use 52697 port if I want to use my network ip
Maybe an ultra-necropost, but as for me, when I needed for some hosts to directly access the server while on the same LAN (it is protected and isolated anyway), I changed line 207
of lib/remote-atom.coffee
from @server.listen port, '127.0.0.1'
to @server.listen port, '0.0.0.0'
.
After Atom restart, works for me.
Maybe a vulnerability if used on unprotected network, but would be nice to have an option to listen on all interfaces.
(If you really know what are you doing, of course, and understand possible implications)
Edit: Alright, I see that it is in latest commit (merged PR), but for some reason Atom installed somewhat older version.
Hi :-), within textmate i have the setting "Terminal -> Accept rmate connections -> Access for: *". I need to set the value to "remote clients", to get a connection between my server and client. Is there any way to configure your plugin to get that setting?
Thanks!