ReadAIrr is a renamed fork of Readarr. Some inherited screenshots, executable names, config keys, API labels, and custom-script environment variables still say
Readarrwhere the current app repo still requires that compatibility name. {.is-info}
Below are the default paths for the application data directory {.is-info}
All instances of
$USERare placeholders for the user the application is running under. {.is-warning}
The default app-data directory still uses inherited Readarr naming in current builds. Treat the paths below as compatibility paths, not branding guidance.
#Windows
C:\ProgramData\Readarr
#Linux
Unless otherwise specified, ReadAIrr stores its application data in the home folder of the user it is running under: /home/$USER/.config/Readarr or ~/.config/Readarr.
The installation instructions specify /var/lib/readarr
#MacOS (OSX)
{#os-x}
/Users/$USER/.config/Readarr or ~/.config/Readarr
#Synology
/usr/local/Readarr/var/.config/Readarr
/volume1/@appstore/Readarr/var/.config/Readarr
#QNAP
/share/MD0_DATA/homes/admin/.config/Readarr
/share/CACHEDEV1_DATA/Readarr_CONFIG
#Docker
/config
- This will vary based on where the user maps
/configto on their host system
#Arguments
The -data= argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is required when trying to run multiple instances. On Windows this would be /data=
The -nobrowser argument refrains from launching/opening the browser on startup. On Windows this would be /nobrowser