transmissiontransfer
This script connects to two instances of transmission using the RPC interface and moves torrents from one to the other.
Example usage:
transmissiontransfer localhost mybooklive.fritz.box –equivalent-path /Volumes/Kiff /shares/Kiff
This will add to the instance running on mybooklive any torrent that is on localhost and that is being saved to /Volumes/Kiff. The resultant torrents will be saved to /shares/Kiff. This allows files stored on an external drive to be migrated to another machine for managing longer term seeding.
For many files, simply re-adding the torrent to the new machine would be enough, however this script also ensures that all files and directories are correctly named, so if a file was renamed in the original torrent client (for example, to fit a local naming convention without breaking seeding) these names will be carried across.
The initial run of this will add any torrents and rename them as appropriate, before triggering a verification run. If it comes across any duplicate torrents that have been successfully verified it will stop them in source and start them in destination.
1 maintainer
Metadata
1 maintainer
Release files for transmissiontransfer 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| transmissiontransfer-0.2.tar.gz | 2.9 kB | Without provenance | Details for transmissiontransfer-0.2.tar.gz |
Release files / transmissiontransfer-0.2.tar.gz
| Download URL | transmissiontransfer-0.2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87e61936129ef0f7c233c857a73f6800d3a28787cf4bacd3a9c428a4117575d0
|
|
BLAKE2b-256 checksum How to use checksums |
506ebbe54113872957a054e06721d58ae551f2aae52b835b31dc56314cdabf2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for transmissiontransfer 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
