Mopidy-Pibox
pibox is a Mopidy HTTP client that allows multiple users to search for and queue songs as a group, via a clean and simple interface.
Features
Search for and queue songs using any Mopidy backend
Vote to skip queued tracks
Plays from predefined playlists if no tracks are queued
Prevents tracks from being queued again after they have been played or skipped
Admins controls to pause/resume playback or skip current track
Display view for showing on a TV or monitor
Suggests songs to queue based on frequently played tracks
Can be used offline without an internet connection using Mopidy-Local
Requirements
A backend for Mopidy such as Mopidy-Spotify or Mopidy-SoundCloud
Installation
Install by running:
pip install Mopidy-Pibox
Start Mopidy:
mopidy
Open your Mopidy URL (e.g. http://localhost:6680) and click Pibox
Configuration
Note: In order to understand if people are using Pibox, GoatCounter is used to track basic usage. It does not store any personal data. If you do not want analytics to be collected, you can disable it by setting the disable_analytics config option to true in your Mopidy config file.
Before starting Mopidy, you must add configuration for Mopidy-Pibox to your Mopidy configuration file:
[pibox] enabled = true offline = false default_skip_threshold = 3 default_playlists = spotify:playlist:79inBfAlnfUB7i5kRthmWL disable_analytics = false
The following configuration values are available:
pibox/enabled: If the pibox extension should be enabled or not. Defaults to true.
pibox/offline: If the extension should be used offline. Defaults to false.
pibox/default_skip_threshold: The default number of votes required to skip a track. Defaults to 3.
pibox/default_playlists: The URIs of the default playlists to play from when starting a new session. Defaults to a Spotify playlist of great party songs. Save it to your Spotify library!
pibox/disable_analytics: Stops GoatCounter analytics from being included in the Pibox web app. Defaults to false.
Project resources
Credits
Original author: Gavin Bannerman
Metadata
Release files for Mopidy-Pibox 4.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mopidy_pibox-4.0.3.tar.gz | 721.6 kB | Without provenance | Details for mopidy_pibox-4.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mopidy_pibox-4.0.3-py3-none-any.whl | Python 3 | none | any | Details for mopidy_pibox-4.0.3-py3-none-any.whl |
Total release size: 988.6 kB
Release files / mopidy_pibox-4.0.3.tar.gz
| Download URL | mopidy_pibox-4.0.3.tar.gz |
|---|---|
| Size | 721.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80eaa4902481be226916a1abc80db160f222f5fc2c1d93f2f15e44b5d3cf3772
|
|
BLAKE2b-256 checksum How to use checksums |
695f3523317b8d1acdc3c568565cccb05898989bdd6e283495972fcaa1398f00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.14.4
|
Release files / mopidy_pibox-4.0.3-py3-none-any.whl
| Download URL | mopidy_pibox-4.0.3-py3-none-any.whl |
|---|---|
| Size | 267.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9e40f5f6149c1b34836e879795dcd1ef26bc48d4db98d007565716ad018a40c
|
|
BLAKE2b-256 checksum How to use checksums |
4d3082352e2815a8500d0ad7378f59d531b5b2ada62c12f899a41ca560df483e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.14.4
|
Security for Mopidy-Pibox 4.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.