storm ghcr.io/relvacode/storm https://github.com/relvacode/storm/pkgs/container/storm bridge sh false https://forums.unraid.net/topic/121929-support-djismgaming-storm-a-self-hosted-mobile-friendly-webui-for-deluge/ https://github.com/relvacode/storm Introducing Storm A slick remote interface for Deluge that fully supports mobile devices (including as a home-screen app) Some neccesary steps: - You'll need a Deluge container running with a valid auth configuration as shown here: https://dev.deluge-torrent.org/wiki/UserGuide/Authentication - Storm needs a way to contact the Deluge RPC daemon so it's best that you create a Docker network and attach the Storm container to that network. - Once that's setup you'll need to configure Deluge to allow remote RPC connections: - Open up core.conf in your Deluge configuration folder - set "allow_remote": true Security By default, Storm does not authenticate requests made to the API. When serving Storm over the public internet you should ensure access to your Deluge daemon is properly secured. - Storm comes with a simple built-in authentication mechanism which can be enabled with the environment variable STORM_API_KEY or the command-line option --api-key. - Set this to a reasonably secure password. Any requests made to Storm must now provide the API key in the request. - You should also seriously consider the use of HTTPS over the internet, with services like LetsEncrypt it's relatively easy to get a valid SSL certificate for free. Downloaders: Status:Stable http://[IP]:[PORT:8221] https://raw.githubusercontent.com/djismgaming/docker-templates/main/djismGAMING/img/storm.png 1649774125 Introducing Storm A slick remote interface for Deluge that fully supports mobile devices (including as a home-screen app) Some neccesary steps: - You'll need a Deluge container running with a valid auth configuration as shown here: https://dev.deluge-torrent.org/wiki/UserGuide/Authentication - Storm needs a way to contact the Deluge RPC daemon so it's best that you create a Docker network and attach the Storm container to that network. - Once that's setup you'll need to configure Deluge to allow remote RPC connections: - Open up core.conf in your Deluge configuration folder - set "allow_remote": true Security By default, Storm does not authenticate requests made to the API. When serving Storm over the public internet you should ensure access to your Deluge daemon is properly secured. - Storm comes with a simple built-in authentication mechanism which can be enabled with the environment variable STORM_API_KEY or the command-line option --api-key. - Set this to a reasonably secure password. Any requests made to Storm must now provide the API key in the request. - You should also seriously consider the use of HTTPS over the internet, with services like LetsEncrypt it's relatively easy to get a valid SSL certificate for free. bridge 8221 8221 tcp DELUGE_RPC_HOSTNAME DELUGE_RPC_USERNAME DELUGE_RPC_PASSWORD v2 DELUGE_RPC_VERSION STORM_API_KEY 8221 v2