Remote Tunnel

[zodern]

Right now the tunnel uses http://localtunnel.me/ and their npm package.

We should switch to @formula1 Silk Server.

ToDo

• Deploy to Exoscale
• Update client api to work with SockJS
• Get a domain
• The server shouldn't crash when the password or local name is wrong

The server is at http://185.19.29.43:2999/.

[zodern]

The tunnel uses a nonstandard port for the tunnel app to communicate with the silk server. Because of the nonstandard port it doesn't work on many of the free PaaS such as heroku.

Exoscale gave us enough credits for up to 18 months of free hosting for this. I have Silk Server running at http://185.19.29.43:2999.

To use:

1. open the tunnel client app
2. Put http://185.19.29.43:3499 in the first text box and a password in the second. Click connect
3. Copy the number at the end of the list item it adds.
4. Go to and http://185.19.29.43:2999/ past the id and insert your password.

Using the master branch everything works remotely except the terminal app.

I have updated the first comment's list.

[zodern]

We now have a domain: silkgui.com.

Remote is at remote.silkgui.com:2999. I will try to switch it to port 80 and get it to work with www.

[zodern]

In NodeOS/NodeOS#79 there is discussions of using reverse proxy to allow remote access. remote.silkgui.com will only need to ask the nodeos address, send a message over websocket to start Silk, and once Silk has started redirect to it.

[formula1]

Interesting, I'll take a look