|
72 | 72 | <div data-md-component="skip"> |
73 | 73 |
|
74 | 74 |
|
75 | | - <a href="#name" class="md-skip"> |
| 75 | + <a href="#torrentfile-manual" class="md-skip"> |
76 | 76 | Skip to content |
77 | 77 | </a> |
78 | 78 |
|
|
337 | 337 | </ul> |
338 | 338 | </nav> |
339 | 339 |
|
| 340 | +</li> |
| 341 | + |
| 342 | + <li class="md-nav__item"> |
| 343 | + <a href="#magnet" class="md-nav__link"> |
| 344 | + Magnet |
| 345 | + </a> |
| 346 | + |
| 347 | +</li> |
| 348 | + |
| 349 | + <li class="md-nav__item"> |
| 350 | + <a href="#rebuild" class="md-nav__link"> |
| 351 | + Rebuild |
| 352 | + </a> |
| 353 | + |
340 | 354 | </li> |
341 | 355 |
|
342 | 356 | </ul> |
|
484 | 498 | </ul> |
485 | 499 | </nav> |
486 | 500 |
|
| 501 | +</li> |
| 502 | + |
| 503 | + <li class="md-nav__item"> |
| 504 | + <a href="#magnet" class="md-nav__link"> |
| 505 | + Magnet |
| 506 | + </a> |
| 507 | + |
| 508 | +</li> |
| 509 | + |
| 510 | + <li class="md-nav__item"> |
| 511 | + <a href="#rebuild" class="md-nav__link"> |
| 512 | + Rebuild |
| 513 | + </a> |
| 514 | + |
487 | 515 | </li> |
488 | 516 |
|
489 | 517 | </ul> |
|
509 | 537 |
|
510 | 538 |
|
511 | 539 |
|
512 | | -<h1 id="name">Name</h1> |
513 | | -<ul> |
514 | | -<li>torrentfile</li> |
515 | | -</ul> |
| 540 | +<h1 id="torrentfile-manual">torrentfile Manual</h1> |
516 | 541 | <h2 id="synopsis">Synopsis</h2> |
517 | 542 | <pre><code>torrentfile [options] <subcommand> [options] <args> |
518 | 543 | </code></pre> |
519 | 544 | <h2 id="description">Description</h2> |
520 | | -<p>torrentfile is a CLI tool for creating, editing, validating, or reviewing Bittorrent files(.torrent). |
521 | | -It supports all current versions of the Bittorrent Protocol files as well as hybrid files. |
522 | | -Has support for generating magnet URI's for meta files.</p> |
| 545 | +<p><strong><code>torrentfile</code></strong> is a command line toolkit for working with Bittorrent files(.torrent). |
| 546 | +Some of the tools available include creating torrent files, editing portions of a |
| 547 | +torrent file, checking the integrity or completeness of downloaded torrent contents, |
| 548 | +displaying details of a torrentfile, generating magnet URLs for torrentfiles, and |
| 549 | +individual or batch rebuilding of torrent contents into their original directory |
| 550 | +structure.</p> |
523 | 551 | <h3 id="options">Options</h3> |
524 | 552 | <ul> |
525 | 553 | <li> |
@@ -605,19 +633,25 @@ <h4 id="info">info</h4> |
605 | 633 | <pre><code>torrentfile info <path> |
606 | 634 | torrentfile i <path> |
607 | 635 | </code></pre> |
608 | | -<p>There are no optional arguments for the info subcommand.</p> |
| 636 | +<p>Display detailed information about a torrentfile such as trackers, |
| 637 | +size of contents, Bittorrent version, any comments left, date the |
| 638 | +torrent file was created and more. There is only one positional perameter |
| 639 | +which is the path to the torrent file and there are no optional arguments.</p> |
609 | 640 | <ul> |
610 | 641 | <li><code>/path/to/*.torrent</code> |
611 | 642 | The relative or absolute path to the torrent file.</li> |
612 | 643 | </ul> |
613 | 644 | <h4 id="edit">edit</h4> |
| 645 | +<p>Edit some of the different information detailed in a torrent file. The fields that |
| 646 | +are editable each have option flags detialed below. Each option identifies the |
| 647 | +field to edit inside the torrent file and what the new value should be. If an |
| 648 | +option is not used then its field will be ommited in the newly created torrent |
| 649 | +file. As such if the file is marked as private and it should remain that way, |
| 650 | +the <code>-p</code> option should be used.</p> |
614 | 651 | <p>alias: <code>e</code></p> |
615 | 652 | <pre><code>torrentfile edit [options] <path> |
616 | 653 | torrentfile e [options] <path> |
617 | 654 | </code></pre> |
618 | | -<p>Each option identifies the field to edit inside the torrent file and what the new value should be. |
619 | | -If an option is not used then its field will be ommited in the newly created torrent file. As such |
620 | | -if the file is marked as private and it should remain that way, the <code>-p</code> option should be used.</p> |
621 | 655 | <ul> |
622 | 656 | <li> |
623 | 657 | <p><code>-a</code> <code>-t</code> <code>--announce</code> <code>--tracker</code> |
@@ -645,14 +679,34 @@ <h4 id="edit">edit</h4> |
645 | 679 | </li> |
646 | 680 | </ul> |
647 | 681 | <h4 id="recheck">recheck</h4> |
| 682 | +<p>Recheck requires two paths as arguments. The first is the path to a torrent file, and |
| 683 | +and the second is a path to the file of directory containing the downloaded data |
| 684 | +from that torrentfile. <code>torrentfile</code> recursively validates each file with the hashes |
| 685 | +contained in the torrentfile, and displays the amount missing frome each file, plus |
| 686 | +a final percentage for the whole torrent at the conclusion. This will display a |
| 687 | +progress bar for each file including missing files. It is also permitted to use |
| 688 | +the contents parent directory which can help for batch processing many torrent files.</p> |
648 | 689 | <p>alias: <code>r</code>, <code>check</code></p> |
649 | | -<pre><code>torrentfile recheck <path/to/*.torrent> <path/to/contents> |
650 | | -torrentfile r <path/to/*.torrent> <path/to/contents> |
| 690 | +<pre><code>torrentfile recheck <*.torrent> <contents> |
| 691 | +torrentfile r <*.torrent> <contents> |
| 692 | +</code></pre> |
| 693 | +<h3 id="magnet">Magnet</h3> |
| 694 | +<p>Generate a magnet URL for a torrent file.</p> |
| 695 | +<p>alias: <code>m</code></p> |
| 696 | +<pre><code>torrentfile magnet <path/to/*.torrent> |
| 697 | +</code></pre> |
| 698 | +<h3 id="rebuild">Rebuild</h3> |
| 699 | +<p>Rebuild individual or batches of torrent contents into the original file structure. |
| 700 | +The program takes a path to a torrent file or directory containing torrent files, |
| 701 | +the directory containing the torrent contents, and the destination directory to |
| 702 | +where the rebuilt torrent content wil be located. The program will recursively |
| 703 | +traverse the content directory searching for file's that match one of the meta files |
| 704 | +and creates copies of the matches to the destination directory. The original files |
| 705 | +are not effected and any existing files in the target directory will not be |
| 706 | +overwritten.</p> |
| 707 | +<p>alias: <code>build</code>, <code>b</code></p> |
| 708 | +<pre><code>torrentfile rebuild <metafiles> <contents> <destination> |
651 | 709 | </code></pre> |
652 | | -<p>There are only two arguments for the recheck command and both are mandatory. The first is the absolute or relative |
653 | | -<code><path></code> to the torrent file, and the second is the absolute or relative <code><path></code> to it's content. This will display a |
654 | | -progress bar and at the end output what percent of the torrentfile's content it found at the path indicated. It is also |
655 | | -permitted to use the contents parent directory as the second argument and the result will be the same.</p> |
656 | 710 |
|
657 | 711 |
|
658 | 712 | </article> |
|
0 commit comments