How to Self-Host Gonic
Gonic lightweight Subsonic-compatible music and podcast server with folder browsing, tag scanning, transcoding, playlists, and multiple users. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Gonic is a good fit
Choose Gonic when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Use the official container or binary, mount the music library read-only, and persist the database, cache, podcasts, and playlists.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up the Gonic database and playlists; treat the source music library as a separate media backup set.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Change the documented default administrator credentials immediately and keep the server behind HTTPS.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
