transmission startup handles setting.json, and possible to have transmission data-dir on mounted volume for persistent state
This commit is contained in:
@@ -1,11 +1,21 @@
|
||||
#!/bin/sh
|
||||
|
||||
if [ -f /config/transmission/settings.json ];
|
||||
if [ ! -z "${KEEP_TRANSMISSION_STATE}" ]
|
||||
then
|
||||
echo "STARTING TRANSMISSION: Using custom config directory /config/transmission"
|
||||
exec /usr/bin/transmission-daemon -g /config/transmission/ &
|
||||
echo "STARTING TRANSMISSION: Using transmission-data subdirectory to your /data mount point to store state."
|
||||
|
||||
# Initialize settings from environment variables
|
||||
dockerize -template /etc/transmission-daemon/settings.tmpl:/data/transmission-data/settings.json \
|
||||
true
|
||||
|
||||
exec /usr/bin/transmission-daemon -g /data/transmission-data/ &
|
||||
else
|
||||
echo "STARTING TRANSMISSION: No configuration provided, using defaults"
|
||||
echo "STARTING TRANSMISSION: Storing state in container only."
|
||||
|
||||
# Initialize settings from environment variables
|
||||
dockerize -template /etc/transmission-daemon/settings.tmpl:/etc/transmission-daemon/settings.json \
|
||||
true
|
||||
|
||||
exec /usr/bin/transmission-daemon -g /etc/transmission-daemon/ &
|
||||
fi
|
||||
|
||||
|
Reference in New Issue
Block a user