Emptytree Seedy Manual
Chapter 3 - Configuration

3.1 Steps

3.1.1 Configurator

Kick off a configurator with:

     $ emptytree-seedy

This can be done on any host with a booted system (see Booting for the first time, Section 2.5). If no configuration has yet to be done a configuration window will automatically appear. If not select View --> Show Configuration from the menu.

3.1.2 General Tab

3.1.2.1 Hosts

Every host in the system has to have an entry here, before they can be added (or changed) however they need to have a booted system (see Booting for the first time, Section 2.5).

3.1.2.2 Music Directories

Where the music will reside. The music directories must be exported between the hosts with the same path name.

3.1.2.3 Encode rates

Choose the Rate or Rates at which you want your music encoded.

3.1.3 Database Tab

3.1.3.1 Local database

See Local Database?, Section 3.2 for the relative merits of configuring a local database.

3.1.3.2 Remote CDDBP database

Gets CD information from a freedb server. http://www.freedb.org/.

3.1.4 Host Tab

3.1.4.1 Main

Only one host can be the main host. As desccribed above this is typically a server machine that is left running most of the time or at least most of the time the other hosts are running, it may also be the host upon which the encoded songs will reside.

3.1.4.2 Players

Add a player for every soundcard on the host. For Play Using first try the OSS driver. If it doesn't work or you experience gaps in playback try the decoder option. For the decoder option you may need to specify a Play Buffer because one is not used by default.

3.1.4.3 Cdroms

Add a Cdrom for every cdrom device on the host.

3.1.4.4 Encoders

Add an Encoder for every CPU in the machine.

3.2 Local Database?

If you are not planning on using emptytree-seedy for your music listening needs then the local database will be of no use to you and you can save yourself some time and effort by not setting one up. The local database has two main arguments for using it:

Playlists

Playlists are saved in the database, without one configured they cannot be saved.

Play stats

Play stats are saved in the database, without one configured they cannot be saved.

Future meta information, statistic gathering and querying will probably also rely on a local database.

Posgresql is used for the local database and it needs to be installed on your main host. Allow TCP access typically by editing /etc/postgresql/postmaster.init and enabling:

         PGALLOWTCPIP=yes
         PGPORT=5432

And by editing /etc/postgresql/pg_hba.conf to allow your other hosts to access the database. Consider your system security before doing this.

Create a user for database access that has permission to create databases. Typically done by changing user to `postgres', executing `psql' and then:

       CREATE USER music WITH PASSWORD changeThis CREATEDB NOCREATEUSER;

This is the user and password you will use when configuring local database access. On every host install the Perl module DBI + the DBI database driver DBD::Pg.

Emptytree Seedy Manual