storm
Storm is a lightweight, mobile-friendly remote web interface for the Deluge BitTorrent client, letting you monitor, start, stop, and manage your downloads…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
24/100 Low
- Maintained
- 0last commit 1267 days ago
- Popular
- 45167 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 404 GB minimum RAM, runs on ARM
Availability: platform listings confirmed today, links checked 38 days ago
- GitHub stars
- 167
- Open issues
- 18
- Last commit
- 2023-06-03
- Latest release
- v1.3.0
- License
- MIT
- Activity
- stale
Checked 12 days ago - source: GitHub (relvacode/storm)
Resources & Compatibility
Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Allow port 8080 for Storm UI and REST API Open or allow port 8080 on the machine or in your firewall so you can reach Storm's web UI and REST API. If this port is blocked, you may not be able to submit, watch, or rebalance topologies from a browser or tool. source
- Set GPU resources on supervisor nodes If you plan to use GPUs, add a setting on each supervisor node — the machine that runs your tasks — such as supervisor.resources.map: {"gpu.count": 2.0}. Without it, Storm does not know how many GPUs are available and GPU topologies may fail to start. source
- Start log viewer for event logs If you turn on event logging, run bin/storm logviewer from the Storm installation folder so you can view the detailed messages your topologies logged. Without it, that event information is not displayed, which makes debugging harder. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which port should be opened for Storm's web UI and REST API?
Open or allow port 8080 on the machine or firewall. If the port is blocked, submitting, watching, or rebalancing topologies from a browser or tool may fail.
What supervisor setting is required for GPU resources?
Set supervisor.resources.map on each supervisor node, such as gpu.count set to the number of available GPUs. Without it, Storm does not know how many GPUs are available and GPU topologies may fail to start.
How do I view event logs after enabling event logging?
Run bin/storm logviewer from the Storm installation folder. Without it, event log details are not displayed, which makes debugging harder.
Where should users report bugs or propose features?
Use GitHub Issues. If you do not have an account, you need to create one.
Answers sourced from github.com, storm.apache.org, storm.apache.org, storm.apache.org
Community
Collected today - public community threads