You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I had the same problem as in #14 and applied the same solution as in your comment, but it creates "ghost" directories inside appdata on the container host. Furthermore containers from LinuxServer.io and hotio.dev use /config path for application files and I would like to apply the same approach for Trailarr.
Describe the solution you'd like
Create an APP_DATA environment variable to specify the path for the Trailarr files. If it is not specified, then use the default path /data.
Describe alternatives you've considered
When path mapping is implemented, I assume that I will be able to mount the Sonarr and Radarr media folders under /media and redirect their paths there, that is, it will not interfere with /data.
Additional context
Right now my docker-compose.yml looks something like this:
sunrize
changed the title
[Request] Add ability to change the '/data' directory to another one, for example '/config'
Add ability to change the '/data' directory to another one, for example '/config'
Aug 9, 2024
Is your feature request related to a problem? Please describe.
I had the same problem as in #14 and applied the same solution as in your comment, but it creates "ghost" directories inside
appdata
on the container host. Furthermore containers from LinuxServer.io and hotio.dev use/config
path for application files and I would like to apply the same approach for Trailarr.Describe the solution you'd like
Create an
APP_DATA
environment variable to specify the path for the Trailarr files. If it is not specified, then use the default path/data
.Describe alternatives you've considered
When path mapping is implemented, I assume that I will be able to mount the Sonarr and Radarr media folders under
/media
and redirect their paths there, that is, it will not interfere with/data
.Additional context
Right now my
docker-compose.yml
looks something like this:With
APP_DATA
environment variable, it will look like this:The text was updated successfully, but these errors were encountered: