papagaYO

Host your own papagaYO

papagaYO runs on hardware you already have. Pick the setup that fits; you can move to another later without losing your history.

On your computer

The papagaYO Server app for Windows, macOS and Linux is in testing. It bundles the server and papagaYO Library: choose your music folder, create your account, and open the address it shows on your phone.

Docker

Needs Docker with Compose. Put your music anywhere on the host and point MUSIC at it.

git clone <papagaYO repository> papagayo && cd papagayo
MUSIC=/path/to/your/music docker compose -f deploy/home.compose.yaml up -d
# open http://<this machine>:8000 and create the owner account

The compose file runs papagaYO and papagaYO Library side by side and connects them automatically. Accounts, history and settings live in the data folder next to the compose file.

papagaYO Library: your own folder of music

Already running papagaYO without Jellyfin? Run papagaYO Library where the music lives and connect it under Settings > Jellyfin.

pip install ./library
papagayo-library --music "/path/to/Music"        # first run saves the folder
papagayo-library --show-credentials              # URL, user id and API key for papagaYO

MP3, FLAC, AAC/ALAC, Ogg, Opus, WAV and AIFF. Rescans every 15 minutes; optional ffmpeg converts songs a device can't play.

Proxmox and HTTPS

The recommended always-on setup: a Debian VM (2 vCPU, 4–8 GB RAM, 40 GB disk) with Docker, Caddy for HTTPS, and DuckDNS or your own domain. The full guide covers backups, upgrades, resource limits and recovery.

Reaching your server away from home

Phones and TVs away from home need an address they can reach. Use Tailscale if all your devices can join your private network, or a domain or DuckDNS name with HTTPS when people need an ordinary web address. papagaYO apps require HTTPS outside your home network.