* Add Transmissionic Web UI & New Documentation (#2589)
* Added step to build a .deb file to install and reduce image size (#2590)
* Added step to build a .deb file to install and reduce image size
* Fixed deb install incorrectly done
* Check for update-port script existing instead of being executable (#2593)
#2459
* Fixed TWC paths (#2600)
* add docker build caching to workflow (#2609)
* Privoxy eth0 fixes, healthcheck comparison tweak and start.sh update (#2610)
* by checking for existence of default 127 address,healthcheck will never effectively run, as the non-default eth0 ip will never be matched
* the comparison was not trimming off the port, thus healthcheck was always going to fail or denote a change when there may have been none
* simplified the comparison (thanks @edgd1er )
* Strip double quotes from umask check (#2601)
* Fix problem with enabled UFW with Random Ports (#2603)
Fixing #2255
* move vpn config download to /config (#2592)
* move vpn config download to /config
* fix git safe dir permissions
* cleanup vpn config clone
* re-add zip dl, set git to default
* use alpine:latest for TransmissionUIs build stage (#2573)
* Update fetch-external-configs.sh
removed duplicate bracket
* Update to transmission 4.0.4
* Update configure-openvpn.sh
---------
Co-authored-by: Anastasiya Polina Soyka <apsoyka@protonmail.com>
Co-authored-by: Geoff <geoff@gapple.ca>
Co-authored-by: ksurl <ksurl@users.noreply.github.com>
Co-authored-by: HeavyGee <133152184+heavygee@users.noreply.github.com>
Co-authored-by: WitchRecipe <77073792+WitchRecipe@users.noreply.github.com>
Co-authored-by: Florian Kretschmer <19738301+Entepotenz@users.noreply.github.com>
* Fixed typo in line 95
`form` to `from`
* supported setting DISABLE_PORT_UPDATER to false
previously DISABLE_PORT_UPDATER had to not exist..now it can also be set to false
* Fix minor typos (#2074)
* Fixed missing $ from UFW variable use
There were a number of variable references missing $
* Fixed some more variables missing $
* Removed outdated typeset
this fixes and closes#2095
* add capability for routes-post-start.sh
* update docs
* amended position
placed entry where it should be in logical order when thinking about container lifecycle
Co-authored-by: Kobi <kobirosenstein@gmail.com>
Co-authored-by: Kristian Haugene <haugene@users.noreply.github.com>
Co-authored-by: Patrick Kishino <patrick.a.kishino@gmail.com>
Co-authored-by: Sean Kelly <xconverge@users.noreply.github.com>
* DEBUG: print all lines before execution
if var DEBUG is set to anything other than false, each bash script will be run with a set -x. This would ease debugging
* DEBUG: centralize commands in utils.sh
* Add openvpn-post-config hook
Adds a script check for /scripts/openvpn-post-config.sh, designed so you can make any custom changes to the selected openvpn config file after everything else is ready.
* Update config documentation
Added openvpn-post-config to the documentation. Not sure if openvpn-pre-start should be edited to say before the configuration is processed.
* Fix typo
Serves me right for making changes before bed.
`PEER_DNS` previously was using 'yes/no', but the standard is 'true/false'. This realigns
#1819 to that standard.
For `PEER_DNS_PIN_ROUTES`, no one should be effected by the configurable change- it's been in
the dev branch only for a few days.
`PEER_DNS` however, has been available for users for a few months now, and users have
been told to use `PEER_DNS=no` in places like #1713 or #1667 . Realigning the boolean definition
here is 'a breaking change' technically, although it's my strong suspicion that #1819 fixed
the underlying problem that warranted users using `PEER_DNS=no` in the first place.
I defer to the codebase owner's opinion for how they want this to be handedl.
* docs: add PEER_DNS documentation
#1713 Added dnsleak protections, but didn't document the escape hatch to
disable it. This adds that documentation.
* fix: pin routes for DNS if PEER_DNS is active.
See #1667 for context and user's impacted; PIA for example advertises DNS
servers in the 10.0.0.0/8 range (10.0.0.243 for example). If the home
LAN is 10.0.0.0/8- common- they'll have `LOCAL_NETWORK=10.0.0.0/8` which
will pin a prefer to route through the eth rather than tunnel. The end
result being that DNS is unreachable since the tunnel must be used to reach
said DNS.
This commit modifies tunnelUp.sh such if we honor DNS routes given by the
provider, we force the route to that IP to go through the tunnel; this
overrides any local net range conflict that may occur.
Finally, this behaviour can be suppressed via `PEER_DNS_PIN_ROUTES=no`.
* fix: Add explicit dockerfile env defaults for PEER_DNS*
* Bundle Flood WebUI
Add the Flood WebUI to the default installation of the container.
The Flood UI offers no pre-built tarball for installation, so the source
is cloned and compiled in a separate stage container. Then the resulting
build files are copied to the final image. Build size only increases by
~1MB, but build times are slightly longer due to the added complexity.
Resolves#1661
* Update docs to include new supported WebUI
* Added additional configuration options to table
I had a hard time finding a list of "transmission options" so I ended up looking through the set environment variables in the container to find the two that I was looking for (idle limits)
* Update env var wording
