--without-gtk Don't build GTK+ client (Disobedience)
--without-python Don't build Python support
- See README.client for setting up a standalone client.
+ See README.client for setting up a standalone client (or read the
+ disobedience man page).
+
+ The server is only built by default under Linux. See README.mac concerning
+ its use under OS X.
2. Install it. Most of the installation is done via the install target:
make installdirs install
- The CGI interface has to be installed separately, and you must use Libtool
- to install it. For instance:
-
- ./libtool --mode=install install -m 755 clients/disorder.cgi /usr/local/lib/cgi-bin/disorder
+ The CGI interface has to be installed separately:
- Depending on how your system is configured you may need to link the disorder
- libao driver into the right directory:
-
- ln -s /usr/local/lib/ao/plugins-2/libdisorder.so /usr/lib/ao/plugins-2/.
+ install -m 755 clients/disorder.cgi /usr/local/lib/cgi-bin/disorder
3. Create a 'jukebox' user and group, with the jukebox group being the default
group of the jukebox user. The server will run as this user and group.
Do not use a general-purpose user or group, you must create ones
specifically for DisOrder.
- Under OS X, make sure that ~jukebox/Library/Logs/CrashReporter/ (or
- whatever) exists and is writable by the jukebox user.
-
- mkdir -p ~jukebox/Library/Logs/CrashReporter
- chown -R jukebox:jukebox ~jukebox/Library
-
4. Create /etc/disorder/config. Start from examples/config.sample and adapt it
to your own requirements. In particular, you should:
* add 'player' commands for any file formats not supported natively
suitable; install it in /etc/init.d, adapting it as necessary, and make
appropriate links from /etc/rc[0-6].d.
- For Mac OS X 10.4, you can install server/uk.org.greenend.rjk.disorder.plist
- into /Library/LaunchDaemons. Having done this reload the contents:
-
- sudo launchctl load /Library/LaunchDaemons
-
- Note that the RunAtLoad key has been deliberately commented out, if you want
- to start the server at boot time you must edit this.
-
- If you have a some other init system then you are on your own.
-
-7. Make sure the state directory (/var/disorder or /usr/local/var/disorder or
- as determined by configure) exists and is writable by the jukebox user.
-
- mkdir -m 755 /var/disorder
- chown disorder:root /var/disorder
-
- If you want to use some other directory you must put use the 'home' command
- in the configuration file.
-
-8. Start the server.
+7. Start the server.
On Linux systems with sysv-style init:
/etc/init.d/disorder start
- On Mac OS X 10.4:
-
- sudo launchctl start uk.org.greenend.rjk.disorder
-
By default disorderd logs to daemon.*; check your syslog.conf to see where
this ends up and look for log messages from disorderd there. If it didn't
start up correctly there should be an error message. Correct the problem
and try again.
-9. After a minute it should start to play something. Try scratching it, as any
+8. After a minute it should start to play something. Try scratching it, as any
of the users you set up in step 5:
disorder scratch
The track should stop playing, and (if you set any up) a scratch sound play.
-10. Add any other users you want to config.private. Each user's password
- should be stored in a file in their home directory, ~/.disorder/passwd,
- which should be readable only by them, and should take the form of a single
- line:
+9. Add any other users you want to config.private. Each user's password
+ should be stored in a file in their home directory, ~/.disorder/passwd,
+ which should be readable only by them, and should take the form of a single
+ line:
- password MYPASSWORD
+ password MYPASSWORD
- (root doesn't need this as the client can read it out of config.private
- when running as root.)
+ (root doesn't need this as the client can read it out of config.private
+ when running as root.)
- Note that the server must be reloaded (e.g. by 'disorder reconfigure')
- when new users are added.
+ Note that the server must be reloaded (e.g. by 'disorder reconfigure')
+ when new users are added.
- Alternatively the administrator can create /etc/disorder/config.USERNAME
- containing the same thing as above. It can either be owned by the user and
- mode 400, or owned by root and the user's group (if you have per-user
- groups) and mode 440.
+ Alternatively the administrator can create /etc/disorder/config.USERNAME
+ containing the same thing as above. It can either be owned by the user and
+ mode 400, or owned by root and the user's group (if you have per-user
+ groups) and mode 440.
- You can use 'disorder authorize' to automatically pick passwords and
- create these files.
+ You can use 'disorder authorize' to automatically pick passwords and
+ create these files.
-11. Optionally source completion.bash from /etc/profile or similar, for
+10. Optionally source completion.bash from /etc/profile or similar, for
example:
. /usr/local/share/disorder/completion.bash