Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/erindru/m2t
Magnet to Torrent converter webservice
https://github.com/erindru/m2t
Last synced: about 1 month ago
JSON representation
Magnet to Torrent converter webservice
- Host: GitHub
- URL: https://github.com/erindru/m2t
- Owner: erindru
- License: other
- Created: 2013-03-10T06:22:13.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2020-12-19T04:20:17.000Z (almost 4 years ago)
- Last Synced: 2024-08-06T03:03:23.417Z (3 months ago)
- Language: Python
- Size: 286 KB
- Stars: 61
- Watchers: 7
- Forks: 16
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
m2t - Magnet to Torrent converter
Overview
--------
m2t is a simple service for converting magnets to torrents. It is written in Python/MySQL and uses the bottle web framework and libtorrent bindings.Installation
------------
Prerequisites:1. Python 2.7 / bottle web framework (`pip install bottle`)
2. libtorrent-rasterbar >= 0.16.8 + python bindings (I had to compile my own because Ubuntu was bundled with an old version and I needed the add_magnet_uri() function)
3. MySQL serverBasically, what you need to do is create the database structure (defined in `m2t/db/schema.sql`), and then rename `m2t/config.py.default` to `m2t/config.py` and update the settings in that file as appropriate. You can then start the server using `./start.py`
Running
-------By default, executing `./start.py` starts the server on 127.0.0.1. You will then need to configure another webserver to proxy to it (eg apache/mod_proxy or nginx). If you wish to eliminate this step, change `bottle_host` in `m2t/config.py` to 0.0.0.0 to run the webserver on all interfaces.
Why
---
Basically, I wanted a magnet to torrent converter that could be used as a service (hence its completely API-based) for [openseedbox](http://openseedbox.com) so metadata about torrents (mainly, the total size) could be known in advance before its added to the backend. This is to prevent things like users exceeding their space limits, because if you dont know the size of the torrent in advance, you dont know if the user will exceed their space limits.