How shithawk/jacobsmusic works
Jacob’s Music is a personal, installable music PWA. A user opens the web app, browses or adds music, and plays tracks; downloaded music and app state can be kept on-device. The app also supports YouTube and SoundCloud streaming, while Caddy serves it locally or over Tailscale/LAN. Catalog generation and offline shell caching are additional capabilities. The app’s implementation is largely concentrated in one file; relationships below are limited to the shown excerpts and README, so unsampled wiring is omitted.
Main entry points: app.js Music interface · Caddyfile Caddy server · sw.js Offline shell
Components 14
Music app
- Music interface
web/app.js - Track browsing
web/app.js - Track playback
web/app.js - Device library
web/app.js - Artist browsing
web/app.js - IndexedDB
Media sources
- YouTube tracks
web/app.js - SoundCloud streaming
web/app.js - Music files
- YouTube catalog
youtube/catalog.json
Delivery
- Offline shell
web/sw.js - Caddy server
Caddyfile
Other components
- Listener
- User device
Connections 13
- Listener → Music interface: uses
README.md - Music interface → Track browsing: renders
web/app.js - Music interface → Artist browsing: renders
web/app.js - Music interface → Track playback: selects tracks
web/app.js - Music interface → YouTube tracks: adds videos
web/app.js - Track playback → SoundCloud streaming: plays tracks
web/app.js - Track playback → YouTube tracks: plays tracks
web/app.js - Music interface → Music files: fetches downloads
web/app.js - Music interface → IndexedDB: writes tracks and files
web/app.js - Music interface → Device library: downloads tracks
web/app.js - Caddy server → Music interface: serves locally
README.md - User device → Caddy server: connects
README.md - Offline shell → User device: caches app shell
web/sw.js