The Firefly Media Server (formerly mt-daap) is a fast DAAP server that is simple to install and even easier to configure. Firefly resides on a single Linux machine that doesn’t have to be a powerhouse. In fact, you can install this lightweight server on Ubuntu Server and you’re almost ready to go. In this article you will see how to do just that – install and configure Firefly Media Server on Ubuntu Server.

Features

The Firefly server has all of the features you will want in a DAAP server:

• Supports Unix/POSIX
• Beta for Windows in the works
• On the fly transcoding of OGG, FLAC, Apple Lossless, and WM
• User-created smart playlist support
• Integrates with iTunes and many other DAAP-supporting media players
• Serve streaming radio stations

Installation

Since we are installing on a Ubuntu Server, the installation is simple:

1. Open up a terminal (or just log into your servers’ console)
2. Issue the command sudo apt-get install mt-daap
3. Enter your user password

That’s it. Now it’s time to set it up.

Configuration file

There is only one configuration file for Firefly: /etc/mt-daapd.conf. This file is quite easy to set up. For a basic DAAP server, out of the box, there is really only one option you must configure. If you open up the configuration file look for the line:

mp3_dir = /home/media/music

This is the line you will need to change to reflect the directory you will serve your media from. For my setup I created a new sub-directory in /opt called music. Do this with the command:

sudo mkdir /opt/media

Now you have to make that directory readable by the DAAP server with the command:

sudo chmod ug+r -R /opt/media

Now all files and sub-directories created with the /opt/media directory will have the proper permissions such that the DAAP server can serve up the files.

Of course what you have just set up is a very basic DAAP server. There are a lot of other options within the configuration file you can set up, such as:

• servername: This is the name your DAAP server will broadcast. By default the server will be listed as Firefly RELEASE_NUMBER HOSTNAME (Where RELEASE_NUMBER is the release number of the Firefly installation and HOSTNAME is the hostname of the server.)
• password protection: This will cause any user attempting to access the DAAP server to have to enter a password in order to see the files.
• port: If you need to use a port other than the default (3689), configure it here.
• extensions: The file types you want to allow to be served by your DAAP server.
• Valid codectypes: These are the configurations for the format conversion. There are already lines for this in the configuration file – you just have to uncomment the ones you want to add for internal conversion.
• rescan_interval: If you want to enable background scanning you need to uncomment this entry and set an interval. This will enable you to add new files without having to restart the DAAP server to pick up the new files. Very handy if you frequently add new files.

There are other configuration options, but those are the ones you will want to focus on first.

Start the daemon

After your configuration file is complete, go ahead and move your media files into the directory and then start the server with the command:

sudo /etc/init.d/mt-daap start

With the server up and running you can fire up a DAAP enabled client, like iTunes or Songbird (Note: Songbird requires the addition of a DAAP add on), and you should automatically see the files on the DAAP server.

Final thoughts

Setting up a DAAP server is a great idea for a small internal network where you want to be able to share out a multi-media library. Anyone looking to set this up, and has a Linux server up and running, would do well to give Firefly a try. The simplicity, size, and speed of this server makes it the perfect candidate.

Related posts

• Songbird 0.7 RC1 Released (3)
• iTunes Music Server pulpTunes (7)
• Winamp iPod Plugin (5)
• View and Edit information of songs with More Tunes (1)
• The Complete Media Player Review (Part 1) (15)

In fact even getting to the web-based administration screen isn’t easy from the Linux point of view. The instructions say point your browser to http://bubba and log in. When using a browser on Linux this will take you to search results for “bubba”. And the only mention of an IP address in the instructions is 192.168.10.1. Since my local network uses 192.168.1.x I couldn’t see the address. So what could I do? Let’s take a look.

Figure 1

Once you have the Bubba 2 plugged in (the instructions are quite clear and simple for this step) your first task is to locate the IP address for the machine. For this I employed Wireshark. As you can see, in Figure 1, there is some external traffic (some of which is from Facebook – must look into that) but the IP address of interest is the .16 address. Since there is a lot of traffic coming from that address it is a safe bet that address is attached to the Bubba 2.

So I point my browser to 192.168.1.16 and voila!, the Bubba 2 network admin screen is up. Wireshark has done its job for the day.

Since the Bubba 2 can stream music there has to be a way to place music into the /home/storage/music folder. Any music in this folder will be served up via DAAP. Problem is, how to get it there? It took me a bit of time, but I found a solution.

The first thing to do is to log into the web admin tool. By default the user/password is admin/admin. You can change this to meet your needs of course. Log in as your admin and click on the Fileserver section. Here you can upload all the music you need. Problem is, you can only load one file at a time (you can’t load directories.) With over 15,000 music files to copy this wasn’t an option. My next attempt found me using FTP to transfer directories to the Bubba 2. This worked to a point. What I now had was a standard user with a directory full of music which could not be streamed. This lead me to my next problem: I couldn’t move the directories from the users ~/ directory to /home/storage/music because of permissions issues.

The work around came about with the help of an external USB hard drive. This is the same drive that contains my entire music collection. By connecting this drive to the Bubba 2 I was then able to copy the entire contents of this drive to the /home/storage/music directory which was then ready for streaming.

Streaming to Linux

Figure 2

The easiest method of listening to the music on the Bubba 2 is with a DAAP-enalbed piece of software. Out of the box Rhythmbox was able to connect to the stream. To do this you right click in an empty area of the left nav where a new menu will open (see Figure 2). In this new menu you will see an entry “Connect to DAAP share”. Select that and enter the IP address of your Bubba 2.

Shortly after you do this, your Shared library will populate with music from your Bubba 2. Listen away.

Final Thoughts

The Bubba 2 isn’t limited to only music streaming. You can share out printers and email as well. But when you’re having to connect from a Linux box, you might have to go through a few more steps than you would with either Windows or Mac. Even with these extra steps, it’s worth it. The Bubba 2 is an outstanding piece of hardware that makes sharing to small networks a snap.

Related posts

• Get To Know Linux: Understanding smb.conf (3)
• Set up your new Ubuntu Server as a Samba Server (3)
• Auto mounting a Samba share in Linux (5)
• You Are Sharing Files (4)
• Yoggie PICO Personal Mobile Security Computer (3)