Skip to main content

Unsonic, the un-Subsonic music server.

Project description

Unsonic, the un-Subsonic music server.


Unsonic is a free drop in replacement for the Subsonic music server. It follows the Subsonic API and is usable with existing Subsonic clients without requiring any adjustment to them.

Unsonic strives to be better at handling music files tags, playing of those songs and use less system resources.

Supported Clients

These are the clients that are known to work well:
  • DSub (Android)
  • JamStash (web)
These clients sort of work with isues:
  • Clementine (Linux desktop)


## TLDR: The uber short version
  • make run

## The longer version

### Development build
  • make devel
  • make devel-db
  • make devel-run
### Release build
  • make release
  • make release-db
  • make release-run
### Tests
  • make tests

Manual Installation

## Building
  • make


  • ./bin/unsonic -c <config.ini> sync
  • ./bin/unsonic -c <config.ini> adduser name pass
  • ./bin/unsonic -c <config.ini> serve [–reload]

Manual Testing

  • ./test/bin/tester getArtists

Installing a Web Client

` [unsonic] ui = ../Jamstash/dist `

  • With Unsonic running, point your browser at the url printed out, normally something like http://localhost:6543 and your will be redirected to the load Jamstash.
  • Jamstash is very picky about the server URL in it’s configuration. Make sure there is no trailing ‘/’ character otherwise Jamstash will not be able to build the path correctly.

Docker Installation

Docker files are located in the ./docker directory. The Makefile contains some convenience targets but the specific docker and/or docker-compose cmmands are also shown.

To build the Unsonic Docker image:

` $ docker build ./docker `

Or using docker-compose:

` $ docker-compose -f ./docker/docker-compose.yml build `

The docker-compose file defines 3 containers, each is geared toward a development/test setup; a production Docker should only use these as a reference. The containers defined are of PostgreSQL, and an Unsonic serve based on PostgreSQL and SQLite. The Unsonic containers requires a music directory to volume mount so one must be specified.

` $ MUSIC_DIR=~/music/ docker-compose -f ./docker/docker-compose.yml create $ MUSIC_DIR=~/music/ docker-compose -f ./docker/docker-compose.yml up Unsonic-postgres `

Or using the Makefile to simplify all of the above.

` $ make MUSIC_DIR=~/music/ docker-sqlite `

See docker/Dockerfile for details about the unsonic image. The container details are defined docker/docker-compose.yml. The files docker/config.ini and docker/unsonic-init can be used to tweak the Unsonic process itself.

Adjusting the configuration

The main configuration settings are the location of the database

` [mishmash] sqlalchemy.url = sqlite:///%(here)s/build/development.sqlite `

and the location of the music directory

` [mishmash] paths = Music: /%(here)s/test/music `

Adjust them to fit your deployment needs. The mishmash.paths can have multiple music directories, one per line. %(here)s refers to the location of the configuration file itself.


Unsonic is licensed under the GPL v2 license. See the COPYING file for details or

************************** CHANGES **************************


  • Initial version

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for unsonic, version 0.1b10
Filename, size File type Python version Upload date Hashes
Filename, size unsonic-0.1b10.tar.gz (50.3 kB) File type Source Python version None Upload date Hashes View hashes

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page