Bind transmission to tun0

[ianneub]

I believe this will solve #11

It forces openvpn to use tun0. Then determines the IP of said interface and updates the settings.json config before starting transmission.

This will not work if the user has created a /data/transmission-data folder and is using that.

Maybe we should get rid of that? The user could simply replace the /etc/transmission-daemon/settings.json with their own file as easily as mounting it to /data.

[haugene]

Yes, looks good!

About the /data/transmission-data, I'm using that one. But it's not for the settings.json, that will be rewritten from the template on every startup anyways. It's because Transmission stores torrent state there, like which torrents are added, active, paused, etc.
I have this container in a docker-compose and I have been tearing down and setting the containers up a lot, then it's nice not to have to add the torrents again.
But... I will admit, it's not that big deal. If people want they can mount the /etc/transmission-daemon as well to keep state. So yes, we should maybe remove it...

Can you recreate the pull request against the dev branch? Then I can make some small modifications as well, before pushing new version.