ruTorrent is a front-end for the popular Bittorrent client rtorrent.
This project is released under the GPLv3 license, for more details, take a look at the LICENSE.md file in the source.
ruTorrent itself needs to be configured. Instructions can be found in various articles in the wiki.Pull requests target master. There is no develop branch — it was retired,
and a release is simply a tag on master.
Using AI tooling to write a patch is fine. Opening what it produced without reading it is not. Whatever wrote the code, the pull request is yours, and that means three things before you open it:
Keep the diff scoped to the change. Whitespace churn, unrelated reformatting and rewritten vendored files make a patch unreviewable, and a patch nobody can review does not get merged.
json and pcre extensions. The simplexml,
curl, mbstring and zlib extensions are recommended — some plugins and the
XMLRPC proxy need them — as are the php, curl and gzip command-line
programs.0.9.8 baseline and the 0.16.x series are supported.
Other versions may or may not work.A checker is bundled with ruTorrent. Run it from the command line, from inside your ruTorrent directory:
php env_check.php
It verifies the PHP version and extensions, the external programs plugins rely
on, common conf/config.php mistakes, and connects to rtorrent to report and
classify its version and to check that ruTorrent's event handlers are registered
with it. It exits 0 when everything required passes and 1 otherwise, so it
can be used in scripts. For safety it runs on the command line only and refuses
to run under a web server.
(top 30 of 162)
JavaScript
57.0%
PHP
36.3%
CSS
5.8%
ruTorrent is a front-end for the popular Bittorrent client rtorrent.
This project is released under the GPLv3 license, for more details, take a look at the LICENSE.md file in the source.
ruTorrent itself needs to be configured. Instructions can be found in various articles in the wiki.Pull requests target master. There is no develop branch — it was retired,
and a release is simply a tag on master.
Using AI tooling to write a patch is fine. Opening what it produced without reading it is not. Whatever wrote the code, the pull request is yours, and that means three things before you open it:
Keep the diff scoped to the change. Whitespace churn, unrelated reformatting and rewritten vendored files make a patch unreviewable, and a patch nobody can review does not get merged.
json and pcre extensions. The simplexml,
curl, mbstring and zlib extensions are recommended — some plugins and the
XMLRPC proxy need them — as are the php, curl and gzip command-line
programs.0.9.8 baseline and the 0.16.x series are supported.
Other versions may or may not work.A checker is bundled with ruTorrent. Run it from the command line, from inside your ruTorrent directory:
php env_check.php
It verifies the PHP version and extensions, the external programs plugins rely
on, common conf/config.php mistakes, and connects to rtorrent to report and
classify its version and to check that ruTorrent's event handlers are registered
with it. It exits 0 when everything required passes and 1 otherwise, so it
can be used in scripts. For safety it runs on the command line only and refuses
to run under a web server.
(top 30 of 162)
JavaScript
57.0%
PHP
36.3%
CSS
5.8%