Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

112 lines (78 sloc) 3.07 kb
Acoustid Server
* PostgreSQL 8.4+
* Python 2.6+
* SQLAlchemy
* Psycopg2
* Werkzeug
* Jinja2
* Python-OpenID
* Python-Markdown
* Chromaprint
On Ubuntu you can install all dependencies using the following command:
$ sudo add-apt-repository ppa:luks/acoustid
$ sudo apt-get update
$ sudo apt-get install postgresql postgresql-contrib postgresql-server-dev \
python-sqlalchemy python-werkzeug python-jinja2 \
python-openid python-markdown python-chromaprint \
Compile and install the included PostgreSQL extension:
$ cd postgresql
$ sudo make install clean
$ cd ..
Prepare the configuration file:
$ cp acoustid.conf.dist acoustid.conf
$ vim acoustid.conf
Create the PostgreSQL database:
$ sudo -u postgres createuser acoustid
$ sudo -u postgres createdb -O acoustid acoustid
Install extensions into the newly created database:
$ psql -U postgres acoustid <`pg_config --sharedir`/contrib/_int.sql
$ psql -U postgres acoustid <`pg_config --sharedir`/contrib/pgcrypto.sql
$ psql -U postgres acoustid <`pg_config --sharedir`/contrib/acoustid.sql
Create the database structure:
$ ./ <sql/CreateTables.sql
$ ./ <sql/CreateFunctions.sql
$ ./ <sql/CreatePrimaryKeys.sql
$ ./ <sql/CreateFKConstraints.sql
$ ./ <sql/CreateIndexes.sql
Setup a MusicBrainz slave database (without custom extensions):
$ cd /path/to/mbslave
$ cp mbslave.conf.default mbslave.conf
$ vim mbslave.conf
$ echo 'CREATE SCHEMA musicbrainz;' | ./
$ sed 's/cube/text/i' sql/CreateTables.sql | ./
$ ./ mbdump.tar.bz2 mbdump-derived.tar.bz2
$ ./ <sql/CreatePrimaryKeys.sql
$ vim sql/CreateFunctions.sql # remove functions that mention "cube"
$ ./ <sql/CreateFunctions.sql
$ grep -vE '(collate|page_index|gist)' sql/CreateIndexes.sql | ./
$ ./ <sql/CreateViews.sql
$ ./ <sql/CreateSimpleViews.sql
$ ./
Unit Tests
Before you can run the test suite, you need to create a configuration file
called acoustid-test.conf. This should use a separate database from the
one you use for development, but it should have the same structure. The
simplest way to create it is to copy your development database.
You can then run the test suite like this:
$ nosetests -v
The first thing it does is setting up the database. Normally you shouldn't
need to do this more than once, so the next time you can run the test suite
without the database setup code:
$ SKIP_DB_SETUP=1 nosetests -v
Jump to Line
Something went wrong with that request. Please try again.