-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to override transmission predefined envariable varibles for configuration #1694
Comments
It's hardcoded because the storage volume it also configured on this location. Why do you want to override it? |
Well, because I used to have own app/chart for transmission and I have already few hundred torrents with path set to different folder in container, I managed by adding additional mount, wanted to set it back to default one in config. Moreover I wanted to disable incomplete download, which seems to be tricky too. In general it is possible to take this one out and use it both for config and for mount point in helm template. |
So far if I understand correctly, you want to be able to:
What is the benefit of disabling the incomplete directory? Isn't it better to have it separate so you can for example point that to an faster storage medium? (or just leave it on the same storage medium as downloads) This could probably be added as an option. But how transmission will handle this: User installs app with incomplete enabled. Regarding the download path, the reason for making it configurable is for existing torrents that had different paths, right? |
I can change the path on all my torrents, it would require few lines program or script to use transmission API calls. In general i think that all configs saved in configmap limits them to be changed to from within the app as configmaps are readonly, i do understand that default listen address and rpc disabled would make it less user friendly though. |
I was thinking if there was an built-in way to easily achieve that, I don't wanna have users use/write scripts to do that of course!
I'm just looking what are the exact use cases, so I can adapt it best. But also the maintenance part have to be considered. Majority of apps don't "care" where the storage is mounted, and if they do, adjusting the variable, will pick everything up. So exposing everything on every app does not make sense, goal is to make the installer as simple as possible. If you expose too much, then you lose the point of having an "app", as it would be the same as configuring the app via
So what I'm thinking is:
I'm not sure that exposing the rpc toggle is a good idea tho. AFAIK this is for the webui and/or api calls. Is there anything I missed? or something that you think should be handled differently? |
Hi @stavros-k, Thanks for adding this into #1727 There appears to be a bug/issue with it, where the download dir setting is not being set correctly in Transmission. |
charts/community/transmission/1.1.1/templates/_configuration.tpl
Line 10 in 206ce2c
There is no option to change default predefined settings from tpl above.
When adding one of the existing in the definition variables as custom env variables you would get an error:
I assume those should be taken out as parameters to
values.yaml
with defaults, so it would be possible to add them to app edit page. Or need tofor range
over those and avoid adding if it set via custom envsThe text was updated successfully, but these errors were encountered: