nefarious Update transmission-settings.json

I think forcing a default password is a good idea specially for folks who run Nefarious on a cloud hosted server. This would need to be reflected in the readme, happy to submit a pull for that as well. This is being discussed in #159

Dec 30 '21 23:12 Clickbaitcake

I am all for this, but I'd like to consider how to piggy-back off the environment variables defined in .env . I'd like to prevent duplication of configuration but I'll have to think about how this would work.

Ideally, we'd add two new variables in .env that would get passed to Transmission:

TRANSMISSION_USER
TRANSMISSION_PASS

Jan 01 '22 16:01 lardbit

Oh, it looks like the linuxserver/transmission supports USER and PASS environment variables so we can populate them via the .env file.

Jan 01 '22 17:01 lardbit

Thanks for the help pointing this out and coming up with solutions. I still need to test the VPN setup, but https://github.com/lardbit/nefarious/pull/167 sets a default transmission user/pass without requiring the user to modify the transmission-settings.conf file. I'd appreciate it if you could help me verify it works for you as well.

Jan 01 '22 22:01 lardbit