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
Copy file name to clipboardExpand all lines: README.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,6 @@ Find us at:
14
14
*[Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more!
15
15
*[Podcast](https://anchor.fm/linuxserverio) - on hiatus. Coming back soon (late 2018).
16
16
17
-
# PSA: Changes are happening
18
-
19
-
From August 2018 onwards, Linuxserver are in the midst of switching to a new CI platform which will enable us to build and release multiple architectures under a single repo. To this end, existing images for `arm64` and `armhf` builds are being deprecated. They are replaced by a manifest file in each container which automatically pulls the correct image for your architecture. You'll also be able to pull based on a specific architecture tag.
20
-
21
-
TLDR: Multi-arch support is changing from multiple repos to one repo per container image.
[](https://microbadger.com/images/linuxserver/transmission"Get your own version badge on microbadger.com")
@@ -35,7 +29,7 @@ TLDR: Multi-arch support is changing from multiple repos to one repo per contain
35
29
36
30
## Supported Architectures
37
31
38
-
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).
32
+
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
39
33
40
34
Simply pulling `linuxserver/transmission` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
@@ -110,6 +106,7 @@ Container images are configured using parameters passed at runtime (such as thos
110
106
|`-e PUID=1001`| for UserID - see below for explanation |
111
107
|`-e PGID=1001`| for GroupID - see below for explanation |
112
108
|`-e TZ=Europe/London`| Specify a timezone to use EG Europe/London. |
109
+
|`-e TRANSMISSION_WEB_HOME=/combustion-release/`| Specify an alternative UI options are `/combustion-release/` and `/transmission-web-control/`. |
113
110
|`-v /config`| Where transmission should store config files and logs. |
114
111
|`-v /downloads`| Local path for downloads. |
115
112
|`-v /watch`| Watch folder for torrent files. |
@@ -132,6 +129,11 @@ In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as bel
132
129
## Application Setup
133
130
134
131
Webui is on port 9091, the settings.json file in /config has extra settings not available in the webui. Stop the container before editing it or any changes won't be saved.
132
+
133
+
For users pulling an update and unable to access the webui setting you may need to set "rpc-host-whitelist-enabled": false, in /config/settings.json`
134
+
135
+
If you choose to use transmission-web-control as your default UI, just note that the origional Web UI will not be available to you despite the button being present.
136
+
135
137
## Securing the webui with a username/password.
136
138
137
139
this requires 3 settings to be changed in the settings.json file.
@@ -186,6 +188,7 @@ Below are the instructions for updating containers:
186
188
187
189
## Versions
188
190
191
+
***22.02.19:** - Rebase to Alpine 3.9, add themes to baseimage, add python and findutils.
189
192
***22.02.19:** - Catch term and clean exit.
190
193
***07.02.19:** - Add pipeline logic and multi arch.
Copy file name to clipboardExpand all lines: readme-vars.yml
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,9 @@ param_device_map: false
38
38
cap_add_param: false
39
39
40
40
# optional container parameters
41
-
opt_param_usage_include_env: false
41
+
opt_param_usage_include_env: true
42
+
opt_param_env_vars:
43
+
- { env_var: "TRANSMISSION_WEB_HOME", env_value: "/combustion-release/", desc: "Specify an alternative UI options are `/combustion-release/` and `/transmission-web-control/`." }
42
44
opt_param_usage_include_vols: false
43
45
opt_param_usage_include_ports: false
44
46
opt_param_device_map: false
@@ -49,6 +51,11 @@ optional_block_1: false
49
51
app_setup_block_enabled: true
50
52
app_setup_block: |
51
53
Webui is on port 9091, the settings.json file in /config has extra settings not available in the webui. Stop the container before editing it or any changes won't be saved.
54
+
55
+
For users pulling an update and unable to access the webui setting you may need to set "rpc-host-whitelist-enabled": false, in /config/settings.json`
56
+
57
+
If you choose to use transmission-web-control as your default UI, just note that the origional Web UI will not be available to you despite the button being present.
58
+
52
59
## Securing the webui with a username/password.
53
60
54
61
this requires 3 settings to be changed in the settings.json file.
@@ -74,6 +81,7 @@ app_setup_block: |
74
81
# changelog
75
82
changelogs:
76
83
84
+
- { date: "22.02.19:", desc: "Rebase to Alpine 3.9, add themes to baseimage, add python and findutils." }
77
85
- { date: "22.02.19:", desc: "Catch term and clean exit." }
78
86
- { date: "07.02.19:", desc: "Add pipeline logic and multi arch." }
79
87
- { date: "15.08.18:", desc: "Rebase to alpine linux 3.8." }
0 commit comments