Storage and backups
Aurral keeps app state and managed media separate. It also needs compatible filesystem views of Lidarr, your download clients, and any playback server.
For the complete mount model, follow Filesystem and mounts. Use the Lidarr media root and set the Downloads Folder to a path inside Aurral, such as /data/downloads/aurral.
Storage locations
Section titled “Storage locations”| Path | Contains |
|---|---|
/config |
Database, settings, users, sessions, cache state, playlist jobs, and the default yt-dlp staging directory. Mount it with ./config:/config. Do not share it with other apps. |
/data (or Lidarr’s media root) |
Shared library and downloads. Mount the same host media root here in Aurral, Lidarr, download clients, and playback servers. |
| Downloads Folder | Aurral-owned permanent tracks, temporary Flow tracks, imported playlists, and playlist artwork. Set in Settings > Download clients > Downloads Folder > Path (for example /data/downloads/aurral). |
Back up your data
Section titled “Back up your data”- Back up the mounted
/configfolder. - Back up the Downloads Folder if you want to keep generated playlists after a rebuild.
- Back up the Compose file and the environment file that contains your host paths.
yt-dlp stages downloads in /config/_staging by default. You can mount another persistent path and select it under Settings > Download clients > yt-dlp > Staging path. Keep it outside media-server libraries to avoid scanner activity while files are incomplete.
Library safety
Section titled “Library safety”- Aurral does not write into your root music library.
- Artist and album changes go through Lidarr.
- Aurral-owned media stays under the Downloads Folder path. Flow files use
_flows; permanent tracks use the canonicalartist/album/tracklayout.