| 1 | Setting up a standalone DisOrder client |
| 2 | ======================================= |
| 3 | |
| 4 | It is possible to control the DisOrder server over the network if the server |
| 5 | has a 'listen PORT' directive in its configuration file. |
| 6 | |
| 7 | There is currently no standard DisOrder port number. |
| 8 | |
| 9 | |
| 10 | 1. Configure the software with --without-server (and, optionally, |
| 11 | --without-python) and build and install it. Set up a stub config in |
| 12 | /etc/disorder/config (or /usr/local/etc/disorder/config if you didn't |
| 13 | set a nondefault --prefix) with the following contents: |
| 14 | |
| 15 | connect jukebox PORT |
| 16 | |
| 17 | where PORT is the same as 'listen PORT' on the server. |
| 18 | |
| 19 | |
| 20 | 2. Copy the password file for each user to /etc/disorder/config.USER, |
| 21 | the contents being: |
| 22 | |
| 23 | password PASSWORD |
| 24 | |
| 25 | Alternatvely, each user can use ~/.disorder/passwd, with the same contents. If |
| 26 | the DisOrder username differs from the local username then use a 'username' |
| 27 | directive. |
| 28 | |
| 29 | |
| 30 | 3. Test by issuing 'disorder playing'. |
| 31 | |
| 32 | |
| 33 | 4. Run 'disobedience' for the GUI client. |
| 34 | |
| 35 | |
| 36 | The web interface could in principle be made to work on a separate |
| 37 | machine from the main server, though it is unlikely to be efficient |
| 38 | and at the moment it is built whenever the server is, so you will have |
| 39 | to unpick them a bit yourself if you wish to do this. |
| 40 | |
| 41 | |
| 42 | Local Variables: |
| 43 | mode:text |
| 44 | fill-column:79 |
| 45 | End: |