Allow splitting config, downloads and media paths via .env
Some checks failed
Check running / run (push) Has been cancelled
Some checks failed
Check running / run (push) Has been cancelled
Adds optional CONFIG_DIR, DOWNLOADS_DIR and MEDIA_DIR env variables so
users can spread configs, downloads and media across different drives
without restructuring ROOT_DIR. Each falls back to its ROOT_DIR-based
default when left empty, so existing setups keep working unchanged.
The -arr services (sonarr, radarr, lidarr, mylar3) now use a single
${DOWNLOADS_DIR}:/data parent bind with a ${MEDIA_DIR}:/data/media
overlay. This preserves TRaSH's single-/data-mount semantics inside
the container (hardlinks still work on one filesystem) while letting
the host-side media tree live wherever the user wants.
README documents the new variables, the generated folder structure,
recommended storage layouts, and the same-filesystem requirement for
hardlinks between downloads and media.
This commit is contained in:
15
.env.sample
15
.env.sample
@@ -9,8 +9,23 @@ TIMEZONE=Europe/Amsterdam
|
||||
PLEX_CLAIM=
|
||||
|
||||
# Choose your root directory for keeping all your container configs and data.
|
||||
# This is used as the default base path when the more specific *_DIR variables below are left empty.
|
||||
ROOT_DIR=
|
||||
|
||||
# Optional: override individual locations independently of ROOT_DIR. Leave empty to derive them from ROOT_DIR.
|
||||
# Defaults:
|
||||
# CONFIG_DIR = ${ROOT_DIR}/config (per-service config folders)
|
||||
# DOWNLOADS_DIR = ${ROOT_DIR}/data (contains torrents/ and usenet/)
|
||||
# MEDIA_DIR = ${ROOT_DIR}/data/media (final media library: tv, movies, music, ...)
|
||||
#
|
||||
# IMPORTANT: the TRaSH guide relies on hardlinks and atomic moves between downloads and media.
|
||||
# Hardlinks only work when DOWNLOADS_DIR and MEDIA_DIR are on the SAME filesystem. If you put them
|
||||
# on different drives/mounts, Sonarr/Radarr/etc. will fall back to copying, using extra disk space
|
||||
# and time. Split these only if you understand that trade-off.
|
||||
CONFIG_DIR=
|
||||
DOWNLOADS_DIR=
|
||||
MEDIA_DIR=
|
||||
|
||||
# USER IDs for each container that requires their own user. The default values will most likely suffice, but in case one of these IDs is already in use on your system it will have to be changed. Any value should work as long as there aren't conflicts with other users.
|
||||
# If you've already set up the containers and want to change user IDs after the fact, you have to remove the old users first and re-set permissions. First run remove_old_users.sh and then the steps for manual installation.
|
||||
# If you're doing a manual installation make sure to first change the IDs in this file, and then run setup.sh to set up the directory structure and permissions before you start the docker containers.
|
||||
|
||||
Reference in New Issue
Block a user