Tchaik is an open source music organisation and streaming system. The backend is written in Go, the frontend is built using React and Flux.
- Automatic prefix grouping and enumeration detection (ideal for classical music: properly groups big works together).
- Multiplatform web-based UI and REST-like API for controlling player.
- Multiple storage and caching options: Amazon S3, local and remote file stores.
- Import music library from iTunes or build from directory-tree of audio tracks.
- Go 1.4+ (recent changes have only been tested on 1.4.2).
- NodeJS, NPM and Gulp installed globally (for building the UI).
- Recent version of Chrome (Firefox may also work, though hasn't been fully tested).
If you haven't setup Go before, you need to first set a GOPATH
(see https://golang.org/doc/code.html#GOPATH).
To fetch and build the code for Tchaik:
$ go get github.com/tchaik/tchaik/...
This will fetch the code and build the command line tools into $GOPATH/bin
(assumed to be in your PATH
already).
Building the UI:
$ cd $GOPATH/src/github.com/tchaik/tchaik/cmd/tchaik/ui
$ npm install
$ gulp
Alternatively, if you want the JS and CSS to be recompiled and have the browser refreshed as you change the source files:
$ WS_URL="ws://localhost:8080/socket" gulp serve
Then browse to http://localhost:3000/
to use tchaik.
To start Tchaik you first need to move into the cmd/tchaik
directory:
$ cd $GOPATH/src/github.com/tchaik/tchaik/cmd/tchaik
The easiest way to begin is to build a Tchaik library on-the-fly and start the UI in one command:
$ tchaik -itlXML ~/path/to/iTunesLibrary.xml
You can also convert the iTunes Library into a Tchaik library using the tchimport
tool:
$ tchimport -itlXML ~/path/to/iTunesLibrary.xml -out lib.tch
$ tchaik -lib lib.tch
NB: A Tchaik library will generally be smaller than its corresponding iTunes Library. Tchaik libraries are stored as gzipped-JSON (rather than Apple plist) and contain a subset of the metadata used by iTunes.
Alternatively you can build a Tchaik library on-the-fly from a directory-tree of audio files. Only files with supported metadata (see github.com/dhowden/tag) will be included in the index:
$ tchaik -path /all/my/music
To avoid rescanning your entire collection every time you restart, you can build a Tchaik library using the tchimport
tool:
$ tchimport -path /all/my/music -out lib.tch
$ tchaik -lib lib.tch
A full list of command line options is available from the --help
flag:
$ tchaik --help
Usage of ./tchaik:
-add-path-prefix="": add prefix to every path
-artwork-cache="": path to local artwork cache (content addressable)
-auth-password="": password to use for HTTP authentication
-auth-user="": username to use for HTTP authentication (set to enable)
-debug=false: print debugging information
-itlXML="": path to iTunes Library XML file
-lib="": path to Tchaik library file
-listen="localhost:8080": bind address to http listen
-local-store="/": local media store, full local path /path/to/root
-media-cache="": path to local media cache
-path="": path to directory containing music files (to build index from)
-play-history="history.json": path to play history file
-remote-store="": remote media store, tchstore server address <hostname>:<port>, or s3://<bucket>/path/to/root for S3
-static-dir="ui/static": Path to the static asset directory
-tls-cert="": path to a certificate file, must also specify -tls-key
-tls-key="": path to a certificate key file, must also specify -tls-cert
-trim-path-prefix="": remove prefix from every path
Set -local-store
to the local path that contains your media files. You can use trim-path-prefix
and add-path-prefix
to rewrite paths used in the Tchaik library so that file locations can still be correctly resolved.
Set -remote-store
to the URI of a running tchstore server (hostname:port
). Instead, S3 paths can be used: s3://<bucket>/path/to/root
. Set the environment variables AWS_ACCESS_KEY_ID
and AWS_SECRET_ACCESS_KEY
to pass credentials to the S3 client.
Set -media-cache
to cache all files loaded from -remote-store
(or -local-store
if set).
Set -artwork-cache
to create/use a content addressable filesystem for track artwork. An index file will be created in the path on first use. The folder should initially be empty to ensure that no other files interfere with the system.
Development is on-going and the codebase is changing very quickly. If you're interested in contributing then it's safest to jump into our gitter room and chat to people before getting started!