dtcooper/raspotify

A Spotify Connect client that mostly Just Works™

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 13th, 2026
Created on May 23rd, 2017
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 233
Total Stargazers: 5,206 (+0)
Total Subscribers: 65 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Raspotify is a Debian package that wraps librespot as a systemd daemon to turn a Linux device into a Spotify Connect client.

The tool solves the problem of running Spotify Connect on headless Linux systems by packaging the librespot library with systemd integration. It handles the complexity of building and configuring librespot for different architectures, allowing users to install a single .deb file and have Spotify Connect functionality available immediately as a background service. The project supports multiple architectures including ARM variants for Raspberry Pi, standard x86-64, and RISC-V.

Raspotify is designed specifically for headless environments on Debian Stable and compatible systems. It requires a Spotify premium account. The README explicitly recommends alternatives for other use cases: spotifyd for desktop operating systems, and moOde audio player for users seeking a complete turnkey audio solution on Raspberry Pi. The tool does not support ARMv6 processors found in older Raspberry Pi models. Installation is straightforward through pre-built packages, though the README warns against following outdated online guides and directs users to download packages directly.

The project maintains active build infrastructure using Docker for cross-compilation across multiple architectures. The codebase tracks librespot as a git submodule, allowing builds against specific upstream commits while maintaining the ability to bump to newer versions. Documentation is organized in a wiki with dedicated setup guides, and the maintainer actively manages bug reports and feature requests through standard GitHub channels.