Is this a new feature request?
Wanted change
As described in a previous issue this container automatically creates complete and incomplete folders within downloads. If a user has custom/legacy paths for their complete/incomplete directories, these folders reappear every time the container restarts. I would like to be able to have some control over this behavior.
Reason for change
I recently migrated a large (~2000 xfers) transmission environment from Ubuntu to this container. My existing completed download directory is named completed and I would like to continue using that name without the complete dir interfering with my tab complete. The process of rewriting transmission's .resume files to match the complete naming convention is tedious and prone to errors.
Proposed code change
Maybe the mkdir and lsiown commands in the init script & the default settings.json could read these paths from the docker env?
Is this a new feature request?
Wanted change
As described in a previous issue this container automatically creates
completeandincompletefolders withindownloads. If a user has custom/legacy paths for their complete/incomplete directories, these folders reappear every time the container restarts. I would like to be able to have some control over this behavior.Reason for change
I recently migrated a large (~2000 xfers) transmission environment from Ubuntu to this container. My existing completed download directory is named
completedand I would like to continue using that name without thecompletedir interfering with my tab complete. The process of rewriting transmission's.resumefiles to match thecompletenaming convention is tedious and prone to errors.Proposed code change
Maybe the mkdir and lsiown commands in the init script & the default
settings.jsoncould read these paths from the docker env?