Changes between Initial Version and Version 1 of UserGuide/ThinClient

Timestamp:

02/14/2009 05:51:55 AM (15 years ago)

Author:

johnnyg

Comment:

copied from thinclient

UserGuide/ThinClient

@@ +1 @@
+= Thin Client =
+
+[[PageOutline(2-4,,inline)]]
+
+Deluge can be setup in such a way that several machines (clients) can control deluge on a central machine (server) through one of deluge's UI.
+When the client is not on the same private network as the server, it is recommended that only the Web UI is used or that the GTK UI is used with SSH tunneling.
+
+The server setup sections are written for a headless linux server although they could be adapted for other platforms.
+The client setup sections are platform independent.
+
+== GTK UI ==
+
+=== Server Setup ===
+
+==== Without SSH Tunneling ====
+
+ 1. [wiki:Installing Install Deluge] on the server.
+ 1. Run the deluge daemon:
+{{{
+#!sh
+deluged
+}}}
+ You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an InitScript.
+ 1. Run the Console UI:
+{{{
+#!sh
+deluge -u console
+}}}
+ 1. Enable remote connections:
+{{{
+config -s allow_remote True
+}}}
+ This allows other machines besides the localhost to be able to connect to the daemon using the GTK UI.
+ 1. Double check it was set properly:
+{{{
+config allow_remote
+}}}
+ 1. Exit the Console UI:
+{{{
+exit
+}}}
+ 1. Shutdown the daemon:
+{{{
+#!sh
+killall deluged
+}}}
+ 1. Add yourself to the authentication file:
+{{{
+#!sh
+echo "<username>:<password>" >> ~/.config/deluge/auth
+}}}
+ where <username> and <password> are the username and password you intend to use.
+
+ Note: the username and password can be anything - they do not necessarily have to be your server's  username and password.
+
+ 1. Restart the daemon:
+{{{
+#!sh
+deluged
+}}}
+ 1. (Optional) If you do not know your server's private ip, run:
+{{{
+#!sh
+ifconfig | grep -e 'inet addr' | grep -v '127.0.0.1' | cut -f2 -d':' | cut -f1 -d' '
+}}}
+ You will need to know this for setting up the client(s).
+
+Congratulations! The server is now setup for GTK UI access.
+
+==== With SSH Tunneling ====
+
+ 1. [wiki:Installing Install Deluge] on the server.
+ 1. Run the deluge daemon:
+{{{
+#!sh
+deluged
+}}}
+ You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an InitScript.
+ 1. Add yourself to the authentication file:
+{{{
+#!sh
+echo "<username>:<password>" >> ~/.config/deluge/auth
+}}}
+ where <username> and <password> are the username and password you intend to use.
+
+ Note: the username and password can be anything - they do not necessarily have to be your server's  username and password.
+
+ 1. Restart the daemon:
+{{{
+#!sh
+deluged
+}}}
+ 1. (Optional) If you do not know your server's public ip, run:
+{{{
+#!sh
+wget www.whatismyip.com/automation/n09230945.asp -O - 2> /dev/null && echo
+}}}
+ You will need to know this for setting up the client(s).
+
+Congratulations! The server is now setup for GTK UI access using a SSH tunnel.
+
+=== Client Setup ===
+
+==== Without SSH Tunneling ====
+ 1. Run deluge.
+ 1. Go to "Preferences -> Interface" and untick "Enable" under "Classic Mode".
+ 1. Restart deluge. You should now see a connection manager box pop up.
+ 1. Remove the localhost daemon.
+ 1. Click "Add" and enter your server's ip.
+ 1. Leave the port as default.
+ 1. Enter the username & password you added to the authentication file.
+ 1. Click "Add" to add your server's daemon.
+ You should now see a green tick as the status for the host you just added.
+ 1. (Optional) Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up".
+ 1. Click "Connect" and the connection manager pop up box should disappear.
+
+Congratulations! You can now access deluge on the server via the GTK UI.
+
+==== With SSH Tunneling ====
+ 1. Open up a terminal and enter
+{{{
+#!sh
+ssh -fNL 58846:localhost:58846 <server>
+}}}
+ Where <server> is the public ip of your server.
+ 1. Run deluge.
+ 1. Go to "Preferences -> Interface" and untick "Enable" under "Classic Mode".
+ 1. Restart deluge. You should now see a connection manager box pop up.
+ 1. Remove the localhost daemon.
+ 1. Click "Add" and enter "localhost".
+
+ 1. Leave the port as default.
+ 1. Enter the username & password you added to the authentication file.
+ 1. Click "Add" to add your server's daemon.
+ You should now see a green tick as the status for the host you just added.
+ 1. (Optional) Expand "Options" and select "Automatically connect to selected host on startup" and "Do not show this dialog on start-up".
+ 1. Click "Connect" and the connection manager pop up box should disappear.
+
+Congratulations! You can now access deluge on the server via the GTK UI and SSH tunneling.
+
+== Web UI ==
+=== Server Setup ===
+
+ 1. [wiki:Installing Install Deluge] on the server.
+ 1. Run the deluge daemon:
+{{{
+#!sh
+deluged
+}}}
+ You may want to [wiki:Faq#HowdoIstartthedaemonwithloggingenabled enable logging] and/or use an InitScript.
+ 1. Run deluge Web UI:
+{{{
+#!sh
+deluge -u web
+}}}
+ Again, you may want to use an InitScript.
+ 1. (Optional) If you do not know your server's public ip, run:
+{{{
+#!sh
+wget www.whatismyip.com/automation/n09230945.asp -O - 2> /dev/null && echo
+}}}
+
+Congratulations! The server is now setup for web UI access.
+
+=== Client Setup ===
+
+ 1. Open your preferred web browser.
+ 1. Open the URL:
+{{{
+http://<server>:8112
+}}}
+ where <server> is either the private or public ip of the server depending if you are on the server's private network or not.
+
+ 1. Default password is "deluge".
+
+Congratulations! You can now access deluge on the server via the web UI.