PHPackages afk11/magnetdl - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. afk11/magnetdl ActiveApplication[Utility & Helpers](/categories/utility) afk11/magnetdl ============== Download magnet url's using a local Transmission Daemon, and upload using sftp v0.0.3(9y ago)1301MITPHP Since Jul 7Pushed 9y ago1 watchersCompare [ Source](https://github.com/afk11/magnetdl)[ Packagist](https://packagist.org/packages/afk11/magnetdl)[ RSS](/packages/afk11-magnetdl/feed)WikiDiscussions master Synced 4w ago READMEChangelogDependencies (4)Versions (4)Used By (0) ### Magnet downloader [](#magnet-downloader) This application has just one purpose: download torrents and sftp them to another machine. ### Install the application [](#install-the-application) You can CLI tool globally for your user, using composers global feature. ``` composer global install afk11/magnetdl ``` It can be upgraded using: `composer global update` NB: You need to add `~/.composer/bin` to your $PATH for the application to be found. ``` echo "export PATH=~/.composer/vendor/bin:\$PATH" >> ~/.bashrc source ~/.bashrc # this is done automatically when you log in ``` #### Commands: [](#commands) - `magnetdl [magnet url]`: Starts upload procedure - `magnetdlconfig`: Print a default config file to STDOUT ### Install as a library [](#install-as-a-library) Add an entry to your composer.json, or run this in your proect directory: ``` compose require afk11/magnetdl ``` ### Configuration: [](#configuration) You need to configure the software to run it. After installing globally run these: ``` mkdir /home/you/.magnetdl magnetdlconfig > /home/you/.magnetdl/config.json nano /home/you/.magnetdl/config.json ``` Set up the config values and you're good to go! ### Setup Requirements [](#setup-requirements) You will need: - your local machine, running transmission-daemon with the RPC configured. - remote machine with SSH (via keyfile authentication), with some folder you want to write to. om o Disclaimer: The software expects an unencrypted private key as an identity file, as we use `exec()` and can't provide an additional password. If you're worried about compromising the remote machine, the following instructions should help lock things down. 1. Create a group for your user: `shared-jail` 2. Create a new user: `youruser`, and add him to the `shared-jail` group: `usermod -a -G shared-jail youruser` 3. Create an SSH key on your local system, and add the public key to the remote users `/home/youruser/.ssh/authorized_keys` file. 4. Check you can login via SSH from the remote machine: `ssh youruser@yourhost -i /path/to/privatekey 5. Create a basic chroot skeleton, and expose the folder you want to upload to using `mount --bind /sharedfiles /chroot/sharedfiles`. You may need a home directory, but it can be empty. 6. To auto-bind the shared files to the chroot on startup, add this to `/etc/fstab`. /sharedfiles /chroot/sharedfiles none bind Be cautious with this one, errors can cause systems not to boot. 7. Add this to the very bottom of your sshd\_config: Match Group shared-jail ChrootDirectory %h ForceCommand internal-sftp AllowTcpForwarding no 8. Before you log out from the remote system, do `service ssh restart`. 9. Try log in over SSH, you should now get: 'This service allows SFTP connections only.' 10. Try log in over sftp: `sftp youruser@yourhost -oIdentityFile=/path/to/privatekey` and check you're in the chroot, and the folder is accessible. TLDR: Someone with the key can log into the chroot only, and can do anything with the files depending on file permissions. ### Health Score 26 — LowBetter than 41% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity10 Limited adoption so far Community8 Small or concentrated contributor base Maturity55 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~0 days Total 3 Last Release 3645d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/763cdc5cc50414bacd4ff1080eede79432f7c3cc26a3d8aa9031b1537a8bd734?d=identicon)[thomaskerin](/maintainers/thomaskerin) --- Top Contributors [![afk11](https://avatars.githubusercontent.com/u/5617245?v=4)](https://github.com/afk11 "afk11 (4 commits)") --- Tags linksftpdownloaddaemontorrenttransmissionmagnet ### Embed Badge ![Health badge](/badges/afk11-magnetdl/health.svg) ``` [![Health](https://phpackages.com/badges/afk11-magnetdl/health.svg)](https://phpackages.com/packages/afk11-magnetdl) ``` ### Alternatives [friendsofphp/php-cs-fixer A tool to automatically fix PHP code style 13.5k245.4M24.0k](/packages/friendsofphp-php-cs-fixer)[friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 101466.4k45](/packages/friendsoftypo3-content-blocks)[kleiram/transmission-php PHP Transmission client 18517.1k1](/packages/kleiram-transmission-php) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)