AudioDock

Project Overview

AudioDock is a unified local player for music and audiobooks built on modern web technology, covering desktop, mobile, web, and mini-program clients plus a self-hostable backend. It connects to several data sources and ingest protocols, switches seamlessly between audiobook and music modes while remembering each mode's playback state, and supports multi-user and device handoff. The server and web app deploy quickly via containers.

Music and audiobooks in one library that hands off between devices.

Key Features

• Multi-platform: desktop, mobile, web, mini-program, and TV clients
• Multiple data sources: connect to common media-server data sources
• Multiple ingest protocols: support for common streaming and cloud-drive protocols
• Dual-mode switching: one-tap switching between audiobook and music modes with separate playback state
• Multi-user collaboration: multi-user interaction and synchronized playback
• Device handoff: seamless switching between devices
• Metadata parsing: covers and lyrics for tracks with metadata
• Container deployment: deploy the server and web app in containers
• Playback features: lyrics, albums and artists, aggregate search, and a mini player
• Listen and cache: cache while streaming

Target Audience

• Home users who self-host a media library and listen on many devices
• People who want music and audiobooks in one place
• Advanced users who prefer to self-host services

Quick Start

1. Deploy the server: pull the image and configure mounts and environment variables per the sample
2. Copy the web service config to an accessible folder and create the service
3. Open a client and set the backend service address first
4. Register and log in, then refresh the page to browse and play

Core Advantages

• Unified: music and audiobooks share one library and playback system
• Cross-device: data and progress sync and hand off across clients
• Self-hostable: both the server and web app deploy in your own environment

System Requirements

Item	Requirement
Server	a container environment, linux/amd64 recommended
Local development	Node.js 22 or later and pnpm 10 or later
Mobile	build and start from the mobile app directory

Notes

• Deploy and configure the backend address first, then register and log in
• Adjust mount paths and environment variables to your actual layout when deploying
• Only access content you have the right to use