CherryMusic is a music streaming server based on CherryPy and jPlayer. It can be run remotely or on a single computer and is designed to handle huge music libraries (3 TB and more) but also works well with small collections. In contrast to MPD, Icecast and the like, CherryMusic allows multiple users to (individually) login via HTTP/HTTPS using a web browser, browse/search the music database and create/edit playlists and stream music to the browser. From the website:
"CherryMusic is a standalone music server written in python based on CherryPy and jPlayer. It is intended to be an alternative to Last.fm, Spotify, Grooveshark... you name it."
The project is developed on GitHub.
- 1 Installation
- 2 Configuration
- 3 Tips & Tricks
- 4 Troubleshooting
CherryMusic is available in the AUR. There are two packages, the stable release and the development version. If you do not depend on a completely stable version, the development version is recommended, but needs Git for installation.
The latest stable version of AUR.AUR is available in the
For a more up-to-date version with experimental features the CherryMusic development version,AUR, can be chosen. In order to build this version, you need .
Required dependencies are:
Optional dependencies are:
, , , , , (For live transcoding), AUR (For ID3-Tag reading), (For automatic image resizing on displayed cover art)
To just get it up and running with a basic setup, issue:
$ python cherrymusic --setup --port 8080
and open the address "localhost:8080" in your browser (e.g. with Firefox):
$ firefox localhost:8080
This will let you configure the most important options from within the browser and you can set up the admin account.
Start CherryMusic for the initial setup:
On first startup CherryMusic will create its data and configuration files in
~/.config/cherrymusic/, print a note to stdout and exit.
Now, edit the configuration file in
~/.config/cherrymusic/cherrymusic.confand change the following lines to match your setup:
[...] basedir = /path/to/your/music [...] port = 8080 [...]
Open the address "localhost:8080" in your browser (e.g. with Firefox) to create an admin account:
$ firefox localhost:8080
There are many more options to configure, please see this section.
CherryMusic comes with well-documented manpages. see
$ man cherrymusic
$ man cherrymusic.conf
Tips & Tricks
Probably, the most modular and flexible way of populating CherryMusic's music directory (called "basedir") is to create a dedicated directory and only symlink all paths to your music collections into that directory, e.g.:
$ mkdir ~/.local/share/cherrymusic/basedir $ ln -s /path/to/musicdir1 ~/.local/share/cherrymusic/basedir/musicdir1 $ ln -s /path/to/musicdir2 ~/.local/share/cherrymusic/basedir/musicdir2
Running in a GNU Screen session
To keep CherryMusic running after logout, it can be run in a GNU Screen session.
$ screen -d -m -S cherrymusic cherrymusic
Since CherryMusic only writes the output to the GNU Screen session, there is nothing to control from within the session. It may be more convenient to use a systemd service file.
Systemd service file
CherryMusic does not come with a daemon yet. To run it as a system service, the following systemd service file can be used:
[Unit] Description = CherryMusic server After = network.target [Service] User = cherrymusic ExecStart = /usr/bin/cherrymusic PrivateTmp = true StandardOutput = null Restart = always [Install] WantedBy = multi-user.target
This file has to be placed into
$ sudo cp cherrymusic.service /usr/lib/systemd/system/cherrymusic.service
and the permissions should be changed:
$ sudo chmod 644 /usr/lib/systemd/system/cherrymusic.service
Finally, enable and start the service:
$ sudo systemctl enable cherrymusic.service $ sudo systemctl start cherrymusic.service
Note that although the CherryMusic service is now run as the user specified in the systemd service file, the service calls still have to be given as root.
Deactivate flash blocker
An active flash blocker can interfere with the web frontend. If you have trouble with things like track selection or playback, try whitelisting the server in your browser's flash blocker/plugin manager.