@james said in App overwrites manual settings.json changes on restart: Do you think we should change this to be only once one creation I can't speak for everyone, but the idea in my case was to control Transmission remotely using the Tremotesf (https://github.com/equeim/tremotesf-android) mobile app. If you expose the RPC port to the internet, I assume anyone could connect freely, since rpc-authentication-required is explicitly set to false. In that case, having a username and password would definitely help. I guess this isn’t the most common use case, so it's probably fine to skip the app altogether and just manage Transmission through the browser instead. It’s just not as convenient when you don’t have a computer nearby.

There is a difference between using public and private torrent trackers. Private ones are not visible as the public ones are. Another option is to use Cove which can browse and play torrent media from your self-hosted server. Works in the LAMP app.

Latest app info is: [image: 1734598703221-c1b50c2e-5543-491d-9165-bb3a3cb41b3d-image.png]

took me a bit to get around looking into this again. So the values changed in the UI are never synced to the actual config file on disk it seems. They work as long as the process is up. Once transmission is instructed to refresh the settings via killall -HUP transmission-daemon it will reload the values from the config file again. So somehow the web ui needs to trigger a sync to disk, which does not seem to happen.

been right there with ya pal

I pushed out a new package with 4.0.1. Had to bump up the memory limit to 1GB to make things work a bit more reliably.

Setting "script-torrent-done-enabled": false fixes it.

@mehdi Ah ok, familiar with that.. was hoping for some sort of submission system, upload web interface or RSS integration for remote curation.

I can confirm, the intended behaviour is for the files to be hard-linked from /Downloading to /Downloaded. You can do whatever you want with the files in /Downloaded (rename, move it, delete it, whatever), and seeding can continue with the files in /Downloading . Once seeding is complete, it auto-deletes the files in /Downloading. The files in /Downloaded should stay where they are until you do something with them. @txhermit If the behaviour is something else, it's indeed not normal, but also quite surprising since I've been using the app quite a lot without noticing any problems. Do you have any kind of custom configuration or something ?