That’s helpful; this sounds like a docker issue or qBit issue then. The default qBit location for torrents is /downloads, but you’d need to make sure to point it towards the container volume mapping you’re setting up in docker.
my relevant qBittorrent compose volume mapping is as follows:
volumes:
- /volume1/shared/torrents:/data/torrents
Personally, I don’t separate my torrent downloads by type; I use incoming & completed folders. Here’s how I set up my qBittorrent config:
Original Value | New Value |
---|---|
Session\DefaultSavePath=/downloads/ | Session\DefaultSavePath=/data/torrents/1_completed/ |
Session\TempPath=/downloads/incomplete/ | Session\TempPath=/data/torrents/2_incoming/ |
Downloads\SavePath=/downloads/ | Downloads\SavePath=/data/torrents/1_completed/ |
Downloads\TempPath=/downloads/incomplete/ | Downloads\TempPath=/data/torrents/2_incoming/ |
I have a personal Discord server that I drop links into - fully intending to get them out of Discord and into my notes someday, though let’s just say I’m quite behind on that.
Mostly I find it useful because I can drop a link on from my phone and quickly access it from my PC, or vice versa. There is some organization into channel types (food, music, games, etc) but these days I just use a general channel as a dumping ground and figure I’ll sort later, ha.