flood
docker-qbittorrent
Our great sponsors
flood | docker-qbittorrent | |
---|---|---|
47 | 11 | |
2,016 | 845 | |
- | 8.9% | |
7.9 | 8.4 | |
3 days ago | 6 days ago | |
TypeScript | Dockerfile | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flood
-
Show HN: PikaTorrent, a modern, multi-platform, open source BitTorrent app
Why bake libtransmission into the app instead of just using the transmission daemon's RPC?
What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.
I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]
1: https://github.com/transmission/transmission/blob/main/docs/...
1: https://github.com/jesec/flood
2: https://github.com/ronggang/transmission-web-control
-
Looking for a Multi-User Torrent Client...
Only one that I'm aware of is Flood: https://github.com/jesec/flood
-
Self Hosted Roundup # 29
If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.
-
qBittorrent v4.5.1 release
You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/
-
current state of linux clients that can manage 20k+ torrents (~40tb)
One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.
-
Seedbox With Great Mobile Interface?
You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile
-
Feature rich web ui skin with pages
https://flood.js.org/ ?
-
Looking for a torrent setup to seed 5k+ torrents
If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)
-
Beautiful new BitTorrent app just released in beta
qbitorrent-nox with flood-ui
-
Transmission 4.0.0 (Beta 1) - Resource Efficiency & Code Modernization
Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood
docker-qbittorrent
-
We're no longer sunsetting the Free Team plan | Docker
Say I wanted to run this container on k3s. How do I specify PUID, PGID, WEBUI_PORT, and the volumes? This is literally the only thing keeping me from jumping headfirst into k3s. I have no intention of running anything docker in the near future and onwards, but I need to know how I can switch without using something like kompose (I don't want to trust a script with my deployment options, I want to do it by hand like I used to with Docker).
-
Memory leak with linuxserver/qbittorrent Docker container?
Here is a link to an issue I found on the linuxserver/docker-qbittorrent repo discussing the issue I'm currently having.
-
Issue with docker, radarr, and qbittorrent: this directory does not appear to exist.
# https://github.com/linuxserver/docker-qbittorrent qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent network_mode: service:nordvpn environment: - PUID=13002 - PGID=13000 - TZ=${TIMEZONE} - UMASK=002 volumes: - ${ROOT_DIR}/docker/qbittorrent-config:/config - ${ROOT_DIR}/data/torrents:/data/torrents restart: unless-stopped depends_on: - vpn
-
What's the difference in using or not using `network_mode: host`? (example below)
In "docker ps" you'll see the EXPOSE Ports defined in the Dockerfile of your Image. They are only accessable in their own networks unless you just bridge your container to your host's network (not recommended).
-
Where can I find help with Gluetun and Qbittorrent?
My only issue is the the linuxserver/qbittorrent container doesn't always start up after a server reboot, I've just filed a github issue about this: https://github.com/linuxserver/docker-qbittorrent/issues/167
- qBittorrent errors
-
qbittorrent default password?
Check out the GitHub... Nine times out of ten the info is there: https://github.com/linuxserver/docker-qbittorrent
-
Self-hosting all these services on two Raspberry Pi 4s!
qBittorrent
- Problem with torrenting
-
PSA: use older linuxserver/qBittorent stack on docker to resolve WebUI login issue
Stuck on the Login page · Issue #109 · linuxserver/docker-qbittorrent (github.com)
What are some alternatives?
VueTorrent - The sleekest looking WEBUI for qBittorrent made with Vuejs!
docker-wireguard
qBittorrent - qBittorrent BitTorrent client
docker-surfshark - Docker container with OpenVPN client preconfigured for SurfShark
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
openvpn-client
flood-for-transmission - A Flood (https://github.com/Flood-UI/flood) clone for Transmission
authelia - The Single Sign-On Multi-Factor portal for web apps
deluge-web-dark-theme - A modern dark theme for Deluge Web UI with custom accent colours and updated icons.
Paperless-ng - A supercharged version of paperless: scan, index and archive all your physical documents
qbit-matUI - A material WebUI for qBittorrent, written in Angular.
Gotify - A simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui)