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