Live data from Hacker News

Guacamole – HTML5 Clientless Remote Desktop

guac-dev.org

31–40 of 81 posts

Re: Guacamole – HTML5 Clientless Remote Desktop

#32
post #5

Looks promising! Could be use to control bittorrent server from work. Maybe call it pluginless instead? Clientless kinda makes me imagine it's pure js/html5 app but actually it uses a server as client.

you can already control rtorrent via ssh, though admittedly it has a steeper learning curve.

For a less steep learning curve I recommend Deluge's WebUI.

Re: Guacamole – HTML5 Clientless Remote Desktop

#33
post #13
post #11

Earlier quoted context omitted.

Guacamole is a Java program. It's basically a proxy between RDP/VLC and HTML5. Guacd (the java bits) connect to an RDP or VNC server on your behalf, and then you interact with the remote machine through guacd. Here's a simple text diagram [Windows RDP server] [linux Guacamole server] [HTML5 client in your browser]

Wait.. so you're saying you need a linux server to access your windows server?

That seems to be the case. Under "How do I get it?" it says:

> You will need a Linux or UNIX computer to host Guacamole.

Re: Guacamole – HTML5 Clientless Remote Desktop

#34
post #14
post #13

Earlier quoted context omitted.

Wait.. so you're saying you need a linux server to access your windows server?

I'm guessing that since it's java, you can run guacd on either windows or linux.

Only the web application is Java, guacd is written in C:

http://guac-dev.org/doc/gug/guacamole-architecture.html

Re: Guacamole – HTML5 Clientless Remote Desktop

#35
post #5

Looks promising! Could be use to control bittorrent server from work. Maybe call it pluginless instead? Clientless kinda makes me imagine it's pure js/html5 app but actually it uses a server as client.

you can already control rtorrent via ssh, though admittedly it has a steeper learning curve.

Another option could be transmission daemon web ui (forwarded over ssh)

Re: Guacamole – HTML5 Clientless Remote Desktop

#36
post #5

Looks promising! Could be use to control bittorrent server from work. Maybe call it pluginless instead? Clientless kinda makes me imagine it's pure js/html5 app but actually it uses a server as client.

you can already control rtorrent via ssh, though admittedly it has a steeper learning curve.

Or setup a web interface for rtorrent: http://wiki.rtorrent.org/RtorrentProjects#Web_Frontends

And on Android, there's Transdroid: http://www.transdroid.org/

Re: Guacamole – HTML5 Clientless Remote Desktop

#37
post #29
post #12

Earlier quoted context omitted.

It's "clientless" as in you don't have to install any software on the machine you want to connect from. No need to fiddle with RDP software on your parent's computers, or worry about access control restrictions from a locked-down corporate network. As far as permissions go, if you can browse the internet on a computer, you can remote control your servers with Guacamole.

> It's "clientless" as in you don't have to install any software on the machine you want to connect from. Except a browser compatible with HTML5-august-2014-revision. Believe it or not, there are many places stuck in pre-HTML5 times (hotel computers, for example). If it could stream GIFs and accept clicks with server-side image maps, then it would be compatible with every desktop graphical browser in existence (Opera…

> If it could stream GIFs and accept clicks with server-side image maps, then it would be compatible with every desktop graphical browser in existence

I can't decide if that's the most brilliant idea I've ever heard or the most terrifying. Probably both.

Re: Guacamole – HTML5 Clientless Remote Desktop

#39

There already have been a few nice VNC web clients around for a few years, like NoVNC ( http://kanaka.github.io/noVNC/ , python server-side, used in Openstack and others). Unfortunately, there's no magic: you need your VNC/RDP server, then your "clientless server" (proxy socket websocket or alike), then your web server to host the "clientless" client. It's becoming to be interesting when your VNC/RDP client directly…

Note that 1.4 introduced websockets support, VNC support was present much long ago. You would need a proxy tho, like the one NoVNC provides.

I am still waiting better support for Clipboard on QEMU. :/

Currently using NoVNC as a client. Works really well. Keyboard needs more love.

Post reply on HN