Now it's time to install. First we'll modify the mt-daapd.conf file in the contrib directory. The file is well documented, so it should be easy to modify it to suit your needs and specific directory paths. For my directory structure, I created a top-level mt-daapd directory: /share/hdd/data/mt-daapd .
Inside this, I copied the admin-root directory that is used for the web-based configuration and status interface. I created a cache sub-directory for the song database and copied the contrib/mt-daapd .playlist into the mt-daapd directory, modifying the config file accordingly. For my actual music database, I created a top-level MP3 directory and made the configuration file changes to reflect it.
When you've modified the configuration file to suit your needs, copy it to the /share/hdd/conf/etc directory, and create a symbolic link from etc:
Now copy the actual binary, src/mt-daapd , to /share/hdd/conf/bin/. Then move over some music files. I found that the server takes MP3's and AAC files and can scan a directory tree rather than just a flat directory of files. I moved my files over using NFS, but depending on where you put your directory, you can also use SMB or just ftp.
As we did with NFS in my last article, you should create an rc script that creates the symbolic link and starts the actual process. I've been using /etc/rc.d/rc.samba as a starting point. Copy it to /share/hdd/conf/rc.d/rc.mt-daapd, modify it for mt-daapd and start it up:
A quick check of /var/log/mt-daapd .log should show some status messages and issuing a ps -ax command should show mt-daapd running. Don't be alarmed when you see multiple lines in the psoutput for mt-daapd . The mt stands for multi-threaded and Linux will show each thread separately in the output.