A page in your DokuWiki was added or changed. Here are the details: Date : 2013/07/02 01:10 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 87.180.204.24 Hostname : p57B4CC18.dip0.t-ipconnect.de Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing?rev=137... New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing Edit Summary: [X2Go Session Broker Daemon / WSGI] User : sunweaver @@ -28,9 +28,9 @@ ===== X2Go Session Broker Daemon / WSGI ===== Install X2Go Session Broker [[doc:installation:x2gobroker|as described]]. Use a non-X2Go Server for this as installation host (e.g. the central LDAP server). Choosing the right machine on your network for providing X2Go session brokerage heavily depends on your site setup. - You certainly want to make use of SSL (https:// protocol) if the session broker can be accessed from the internet or if you share your network with non-trusted machines. For large scale deployments the WSGI implementation of the broker is recommended (package: ''x2gobroker-wsgi''). For small companies the standalone daemon should probably be fine (package: ''x2gobroker-daemon''). + You certainly want to make use of SSL (https protocol) if the session broker can be accessed from the internet or if you share your network with non-trusted machines. For large scale deployments the WSGI implementation of the broker is recommended (package: ''x2gobroker-wsgi''). For small companies the standalone daemon should probably be fine (package: ''x2gobroker-daemon''). After you have installed the session broker, additionally run the script ''x2gobroker-keygen'' as super-user root: <code bash> -- This mail was generated by DokuWiki at http://wiki.x2go.org/