The first release of version 2 is ready!

⚠️ This version is deprecated. If you'd like to be the maintainer or contributer of this version, please leave a comment here.

Torrent Cloud

A torrent client in the cloud, written in Node.js

There are a various existing cloud torrent services (bitport.io, btcloud.io, put.io), though they're all subscription-based or have limits imposed. Torrent Cloud is intended to be self-hosted on your own cloud compute combined with your own cloud storage. When a file is downloaded, Torrent Cloud simultaneously downloads and uploads the file, so when a torrent is complete, you'll find it in your own storage.

Disclaimer This project was created to bring about an addition download channel to defeat unfair BitTorrent protocol restrictions imposed by enterprises and ISPs. It was intended for downloading legal, non-copywrite material, such as: public linux distributions, personal files, large public statistical datasets, public domain images and videos from archive.org, etc. This project will not take any responsibility for any illegal use, by using this software you agree to these terms.

Features

• Embedded torrent search
• Load torrents via magnet URI or torrent file URL
• Magnet URI editor
• Responsive WebUI (Mobile friendly)
• Download all as streaming ZIP file
• Uses high-bandwidth upload download of cloud providers

Installation

1. Collect the environment variables

   1. Setup your cloud storage (Choose one)

      • AWS

        1. Sign up for a free for 1 year Amazon Web Services account
        2. Go to the AWS Console
        3. Retrieve your API keys (Top-right menu [Your Name] > Security Credentials)
        4. Create an S3 bucket in the region closest to you
        5. You'll need your AWS Access key (AWS_ACCESS_KEY Required)
        6. You'll need your AWS Secret key (AWS_SECRET_KEY Required)
        7. You'll need the S3 bucket name (AWS_BUCKET Required)
        8. You'll need the S3 bucket region code (AWS_REGION Required see region codes)

      • Mega Warning: the Mega backend is quite buggy

        1. Sign up for a free Mega account
        2. You'll need your username (email address) (MEGA_EMAIL Required)
        3. You'll need your password (MEGA_PASSRequired)

      Note: See the contribute section for adding more storage backends

   2. Consider these optional variables

      1. HOST Listening interface (Optional defaults to all 0.0.0.0)
      2. PORT Listening port (Optional default 3000)
      3. AUTH_USER HTTP Basic Auth (Optional default admin)
      4. AUTH_PASSWORD HTTP Basic Auth (Optional if set HTTP auth will be enabled)
      5. SEARCH_PROVIDERS_URL URL to a JSON configuration file (Optional see below)

2. Choose a cloud hosting environment

   1. Heroku

      1. Sign up for a free Heroku account

      2. Click this Deploy button and fill in the variables you've considered above

         

   2. Others

      1. Install Node
      2. $ npm i -g torrent-cloud
      3. env PORT=8080 torrent-cloud

3. And that's it! (On Heroku, visit https://<appname>.herokuapp.com)

You can change these via the Heroku command-line tool or in the Heroku dashboard Apps > App > Config Variables > Reveal > Edit.

Search Providers

Torrent Cloud provides an easy way to screen-scrape any of the copyright-free (legal) torrent sites. The search provider specification can be found here: https://gist.github.com/jpillora/e667f3d16a6bd403edc4. Please add your custom providers in the comment section.

Contributing

Backend A Node.js app using Express, WebSockets, and many other modules. The server entry point is server.js and the modules are inside lib/, they're documented in the comments though questions are welcome via Issues. Currently there are only Mega and AWS storage backends, though contributions are wanted. To get started, take a look at lib/backends/_template.js for the required interface.

Frontend An Angular app with related all files in static/. The HTTP API is for initiating all actions (e.g. start/stop torrent), and will return an error or an empty OK. The entire app state is sent, on change, via WebSockets.

Help!

• Q. If deployment succeeds but the page isn't loading?
• A. View torrent-cloud's stdout. On Heroku, you can view logs with: heroku logs --tail --<appname> (heroku tool required). You're most likely missing one of storage environment variables above.
• Q. Download speed goes up then down?
• A. There is a 50MB buffer, so once the download goes 50MB past the upload, it will stop and wait for the upload to catch up.
• Q. Why is the Mega backend is buggy?
• A. It uses an old library and it hasn't been tested as much as the AWS backend.
• Q. Heroku dynos turn Idle after 30 minutes of no requests?
• A. Use https://uptimerobot.com/ to ping it, you also get the added benefit of tracking its uptime

Ask questions on the Issues page.

Known Issues

• Only supports modern browsers
• Heroku restarts free dynos every day, so your open torrents will be closed once a day. This will also occur every time your app "idles", which can be prevented with a periodic ping, from a service like Uptime Robot, etc. This makes it impossible to download slow torrents over a long period of time.

Todo

• Config file
  • Reconfigurable in UI
• Mega streaming media
• More search providers
• More storage backends
  • Local file system
  • Plex Integration
    • Dropbox
    • Google Drive
    • Copy
    • Box
• More hosting providers
  • Nodejitsu
  • Openshift (Tested though torrent's seem to be unable to connect to the swarm)
• Use backend storage to keep app state between restarts
• Improve UI
  • Make use of screen real estate with mobile in mind
  • Drop-in torrent files
  • Improved file management
    • Save as
    • Rename
    • Folder management
      • Folder UI
• Better download previewers
  • Add Flash fallback for MP3s in Chrome
• Port to Go using anacrolix/torrent

Credits

Built around @mafintosh's awesome torrent-stream.

MIT License

Copyright © 2015 Jaime Pillora <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.