Skip to main content
Upstream source: Current installation guide. Audiobookshelf keeps its SQLite database in /config, artwork and backups in /metadata, and media in the other volumes. No separate SQL Datastore is needed. Keep /config on local storage rather than a network filesystem.

Towbar manifest

.towbar/services/audiobookshelf.service.yml

Configure

  1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration.
  2. Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
  3. Deploy the Service, then perform the checks below before enabling auto-deploy.
  4. Transfer a test audiobook to the server and use docker cp to place it under /audiobooks in the running container. The named volume retains the file when the container is replaced.

Verify

Create a library for /audiobooks, scan and play the test file, then verify the library and listening progress survive redeployment. For field constraints, see Service manifest.
Last modified on September 27, 2026