EZtorrent streamlines content publishing through BitTorrent.
EZtorrent is a program that simplifies the process of publishing content via BitTorrent. With EZtorrent, generating .torrent metainfo files, starting trackers and seeders automates making it incredibly easy to distribute your own files via BitTorrent. Unlike downloading files BitTorrent, distributing your own files via BitTorrent can be a complex process that involves several steps which include generating .torrent metainfo files, starting tracker processes, and starting seeder processes for each individual .torrent file. EZtorrent takes care of all these tasks in one easy step, making it simple to distribute BitTorrent content.
To get started with EZtorrent, you need to download and install BitTorrent according to its instructions. Next, you need to download EZtorrent, unpack the source code, run ./configure, make, and make install. Finally, run the following commands: ezt create mytorrents /var/www/html/torrents /var/mytorrents www.example.com 6969. This will create a list of all files in /var/mytorrents, and a corresponding .torrent file is created for each file, which is then placed in /var/www/html/torrents for publishing over the web with Apache or other HTTP servers.
EZtorrent starts a tracker process running on TCP port 6969, with a seeder for each .torrent file. The DNS name of the machine running EZtorrent in the above example is www.example.com. New files can be added to or removed from /var/mytorrents at any time, with ezt automatically creating any new .torrents that need to be created, removing obsolete .torrents of removed files, and starting or stopping the corresponding seeders.
Besides, it is also possible to create different directories for different sets of files. To do this, you just need to specify a separate TCP port for each directory, and ezt will take care of starting or stopping a separate tracker process for each configured directory and port. All you need to know about using EZtorrent is clearly explained in the INSTALL and NEWS files and the EZtorrent manual page.
For EZtorrent to work, you need to have BitTorrent installed. In the latest version, configure.in fixes the probe for bittorrent-tracker. Overall, EZtorrent simplifies the process of publishing BitTorrent content and eliminates the need to learn about complex steps involving BitTorrent publishing.
To get started with EZtorrent, you need to download and install BitTorrent according to its instructions. Next, you need to download EZtorrent, unpack the source code, run ./configure, make, and make install. Finally, run the following commands: ezt create mytorrents /var/www/html/torrents /var/mytorrents www.example.com 6969. This will create a list of all files in /var/mytorrents, and a corresponding .torrent file is created for each file, which is then placed in /var/www/html/torrents for publishing over the web with Apache or other HTTP servers.
EZtorrent starts a tracker process running on TCP port 6969, with a seeder for each .torrent file. The DNS name of the machine running EZtorrent in the above example is www.example.com. New files can be added to or removed from /var/mytorrents at any time, with ezt automatically creating any new .torrents that need to be created, removing obsolete .torrents of removed files, and starting or stopping the corresponding seeders.
Besides, it is also possible to create different directories for different sets of files. To do this, you just need to specify a separate TCP port for each directory, and ezt will take care of starting or stopping a separate tracker process for each configured directory and port. All you need to know about using EZtorrent is clearly explained in the INSTALL and NEWS files and the EZtorrent manual page.
For EZtorrent to work, you need to have BitTorrent installed. In the latest version, configure.in fixes the probe for bittorrent-tracker. Overall, EZtorrent simplifies the process of publishing BitTorrent content and eliminates the need to learn about complex steps involving BitTorrent publishing.
What's New
Version 1.3: N/A