OpenList can expose files from your own storage over WebDAV. This guide covers a small Docker setup, the WebDAV path, and the handoff to OFPlayer. Check OpenList’s current installation docs for image and configuration changes before deploying. Keep the music folder backed up independently of the OpenList data directory.
1. Prepare storage
Create one directory for OpenList configuration and another for music. The container needs write access to its data directory and read access to your music. Choose a user/group ID with those permissions. For example, from a dedicated project directory:
mkdir -p data
Create docker-compose.yml and replace /path/to/music and the user/group IDs for your host:
services:
openlist:
image: openlistteam/openlist:latest
container_name: openlist
user: '1001:1001'
restart: unless-stopped
ports:
- '5244:5244'
volumes:
- ./data:/opt/openlist/data
- /path/to/music:/opt/openlist/music:ro
environment:
- UMASK=022
The example user must be able to read both mounts and write to ./data. On a system with different ownership, adjust it rather than running the container with elevated privileges by default. Start it with docker compose up -d, then check docker logs openlist for startup and initial account information.
2. Add the music folder
Open http://localhost:5244 from the server or use its LAN address. Sign in to the admin UI, change the initial password, and add a Local Storage mount. Set its mount path to /music and its physical root to /opt/openlist/music. Confirm that the web UI can list your albums before trying WebDAV.
3. Check WebDAV access
OpenList’s WebDAV root is normally http://SERVER:5244/dav/; the mounted music folder is under /dav/music. Use the same account credentials as the web UI. Grant the account WebDAV Read permission so it can list and play files. The exact permission screen can change by release; OpenList’s WebDAV guide is the current source.
Use HTTPS when accessing the server over an untrusted network, and limit who can reach the admin and WebDAV endpoints. A reverse proxy can provide TLS; verify that it forwards WebDAV methods and large media responses. Avoid exposing a password over plain HTTP on the public internet.
4. Connect OFPlayer
In OFPlayer’s source picker, add a WebDAV source. Enter the WebDAV endpoint, username, and password. If the URL already includes /dav/music, leave the optional root path empty unless your setup needs a deeper directory. Test, save, then browse and play a track. Follow the OFPlayer connection guide for errors and current loading limits.
Maintenance
Back up ./data and the original music separately. Pull a reviewed image version and keep a rollback copy of the data before upgrading. If listings are empty, check the container mount, the OpenList storage mount, and WebDAV Read permission in that order. Existing AList deployments should use the migration reference rather than assuming their database can be swapped without a migration step.