How the torrents.csv file looks
infohash;name;size_bytes;created_unix;seeders;leechers;completed;scraped_date # torrents here...
Uploading / Adding Torrents from a Directory
An upload, consists of making a pull request after running the
scan script, which adds torrents from a directory you choose to the
torrent.db file, after checking that they aren't already there, and that they have seeders.
- Torrent-Tracker-Health Dessalines branch
npm i -g dessalines/torrent-tracker-health
Fork this repo.
git clone https://gitea.com/[MY_USER]/torrents-csv-data cd torrents-csv-data # Import the current csv to a sqlite3 db file, to use as a consistent store. ./import_to_sqlite.sh
Scanning a directory
# Run pushd ~/git/torrents-csv-data/tools cargo run --bin scan -- -f ../torrents.db -d MY_TORRENTS_DIR # `MY_TORRENTS_DIR` is `~/.local/share/data/qBittorrent/BT_backup/` for qBittorrent on linux, but you can search for where your torrents are stored for your client. # Export the db back to a torrents.csv file ./export_to_csv.sh # Add your torrents, commit git add torrents.csv git commit -am "Adding [MY_USER] torrents" git push # Now do a pull request
Updating Seeder / Leecher counts
This script will update seeder / leecher counts for torrents with seeders > 0.
pushd ~/git/torrents-csv-data/tools cargo run --bin prune -- -f ../torrents.db -d X_DAYS # `X_DAYS` scrapes torrents that haven't been scraped in X days. # IE 30 will scrape torrents that haven't been scraped in the last month.