The Klipspringer hub, installed as part of the Klipspringer platform is a web server which in turn launches other commands for music playing, streaming, or capturing, each configured as a source. It reads the the source configuration from sources.json and general options from options.json, both of which are in /etc/klipspringer by default.
A starting point for specifying sources and options is to try the example setup, and then adjust the configuration to suit your own system.
Running as direct command
The terminal command klipspringer-hub1 can be run directly from the command line. It doesn’t respond to any commands in the terminal (interaction happens via HTTP), but outputs some diagnostic messages, including a URL for the interface. Options can be supplied on the command line, for instance to specify an audio output device:
klipspringer-hub -joutput "klipalsa:hw:0,1"
Normally, you will want to configure the Klipspringer hub to start automatically, perhaps running as a special user, and direct its output to a log file, but running as a direct command is useful for debugging purposes, in which case you may want to use the option -debug or -debug-full for more diagnostic messages.
Running as a service with systemd
If your operating system has systemd, which most current Linux distributions do, you can deploy the Klipspringer hub as a service with:
sudo systemctl start klipspringer-hub.service sudo systemctl enable klipspringer-hub.service
The first command starts the service immediately, the second one sets it up to be started when the machine boots.
Output from the service can be found in /var/log/klipspringer-hub/output.log and error messages if it fails to start in /var/log/klipspringer-hub/error.log. You need systemd version 240 or newer for logging to work as intended.
Running as an app on macOS
If you installed Klipspringer on a Mac, can find Klipspringer Hub among your normal applications. When you start it, it probably looks like nothing happens, but it launches the Klipspringer hub, redirecting output to ~/Library/Logs/Klipspringer\ Hub.log. So if you have sources and options set up correctly, and if your macOS works as expected (it’s is difficult to predict across versions), it should be accessible at http://localhost:44100 on the same machine, or across the local network if you replace localhost with the name of your Mac.
You add the app to your login items (found under Settings, General) you should get the Klipspringer hub started automatically when you log in after restarting your Mac.
Notes
- The command is a shell script that uses Node.js to launch main.js with parameters that set configuration and library directories