Flood w/ Transmission 3.0.0 on MacOS install issue
FoUStep opened this issue · comments
The only way I could get Flood to work with the default Transmission app for MacOS (no brew, just the dmg download on the site) was by downloading the flood-for-tranmission.zip, opening the package contents of Transmission.app and renamed the current web folder to web.old and created a new folder called web, inserted the contents of the flood-for-transmission.zip and restarting the app.
The location of the web folder:
/Applications/Transmission.app/Contents/Resources
I tried ~/.zprofile (created it) and ~/.zshrc (MacOS default) with adding the export command (including required restarts) but to no avail. Please update the manual for MacOS, or perhaps tell me how to make this work on CLI. Willing to test.
Hi! Thanks for pointing this out. I did some searching and found that you're correct. The readme approach won't really work, it basically hasn't worked like that since Mac switched to zsh as the default I believe.
I think the correct way might be as described by this comment on Stackoverflow. I don't have a Mac so I can't really try it out. Would you mind trying it for me? It would probably be something like:
# To try it once, should apply for any newly started application after this so restart Transmission after it
launchctl setenv TRANSMISSION_WEB_HOME /path/to/your/flood-for-transmission
# To maintain the variable, should apply after a reboot so restart your computer after this and check if Transmission works
launchctl config user TRANSMISSION_WEB_HOME /path/to/your/flood-for-transmission
While your method works I think it's nicer to give the users of this UI the freedom to choice where to put Flood for Transmission.
Do let me know what you find or if you don't want to try this out. ;)
I tried this:
launchctl setenv TRANSMISSION_WEB_HOME /Users/step/Documents/scripts/flood-for-transmission
The command succeeded in the CLI, however it does not result in being able to use Flood. The old web interface is still there even after a restart of the app or in incognito mode (making sure cache is not messing up).
After this I tried the second command to set it persistent for a reboot however the following errors occurred:
launchctl config user TRANSMISSION_WEB_HOME /Users/step/Documents/scripts/flood-for-transmission
This subcommand requires root privileges: config
sudo launchctl config user TRANSMISSION_WEB_HOME /Users/step/Documents/scripts/flood-for-transmission
Usage: launchctl config <system|user> <parameter> <value> When given the "system" argument, modifies the configuration for the system domain. When given the "user" argument on supported platforms, modifies the configuration for all user domains. You must reboot for changes to take effect. Note that if a service specifies a conflicting configuration, the service's parameter will be preferred.
Supported configuration parameters are:
umask <integer as octal>
Modifies the umask(2) applied to services launched in the domain.
path <string>
Modifies the PATH environment variable set on each service in the domain.
You are correct that users are given the option for selecting their own style of web interface. However it was just as easy to rename the current web folder to web.old, as to rename flood-for-tranmission to web and otherwise. To me that's also a good option, but this isn't persistent with an update of Transmission (even though they do not update much). After the renaming of folders, the app does not require a restart or system reboot.
Thanks a lot for trying! Apparently that didn't work, so yeah, perhaps it's nicest to just update the README to instruct the user to do what you did and rename the old folder. Perhaps I will leave a note asking for anyone that knows a better to let me know. I will also add a note to mention that any update of Transmission will overwite the web UI.
Thanks again, I will update the README soon-ish.
If you need me to do more testing, let me know. Thanks for your time and creating a great web interface for Transmission.
Hi! I bumped into a possible alternative. If you have time could you give it a go? Does it work when you run the following in the CLI?
# Replace path with your local path
open /Applications/Transmission.app --args -TRANSMISSION_WEB_HOME "/path/to/flood-for-transmission"
If that doesn't work would you mind also trying with an = between the TRANSMISSION_WEB_HOME variable and the value? Or remove the - before the variable?
If this work I think you should be able to create script that will run Transmission instead. Perhaps still not better anyway, but at this point I'm just curious. ;)
Sourced from: transmission/transmission#1742
So I tried everything you suggested, unfortunately it did not work. I even tried my own variations (extra -, less -, added '', removed "", added = etc etc) but to no avail.
It does not error, it just starts Transmission but it still has the original web interface.
Also I haven't found any documentation on MacOS' CLI arguments from the native app (no brew).
Thanks again for testing. I updated the README instructions. Feel free to let me know if something is still unclear!