README.txt 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133
  1. About BitTorrent:
  2. =================
  3. BitTorrent is a tool for distributing files. It's extremely easy to
  4. use - downloads are started by clicking on hyperlinks. Whenever more
  5. than one person is downloading at once they send pieces of the file(s)
  6. to each other, thus relieving the central server's bandwidth
  7. burden. Even with many simultaneous downloads, the upload burden on
  8. the central server remains quite small, since each new downloader
  9. introduces new upload capacity.
  10. Instructions for users:
  11. =======================
  12. Once you install BitTorrent, you should be able to download .torrent
  13. files. If you have any questions, please read the FAQ:
  14. http://www.bittorrent.com/FAQ.html
  15. If you find a bug, check the FAQ for your bug. If your bug is not in
  16. the FAQ, please send email to:
  17. bugs at bittorrent.com
  18. Instructions for publishers:
  19. ============================
  20. Instructions for trackerless operation are in TRACKERLESS.txt.
  21. To start hosting -
  22. 1) start running a tracker
  23. First, you need a tracker. If you're on a dynamic IP or otherwise
  24. unreliable connection, you should find someone else's tracker and
  25. use that. Otherwise, follow the rest of this step.
  26. Trackers refer downloaders to each other. The load on the tracker
  27. is very small, so you only need one for all your files.
  28. To run a tracker, execute the command bittorrent-tracker.py Here is an
  29. example -
  30. ./bittorrent-tracker.py --port 6969 --dfile dstate
  31. --dfile is where persistent information is kept on the tracker across
  32. invocations. It makes everything start working again immediately if
  33. you restart the tracker. A new one will be created if it doesn't exist
  34. already.
  35. The tracker must be on a net-addressable box, and you must know the
  36. ip number or dns name of it.
  37. The tracker outputs web logs to standard out. You can get information
  38. about the files it's currently serving by getting its index page.
  39. 2) create a torrent file using maketorrent.py (GUI) or
  40. maketorrent-console.py. The GUI version, maketorrent.py is preferred.
  41. To generate a torrent file using maketorrent-console.py and give it the file
  42. you want a torrent for and the url of the tracker
  43. ./maketorrent-console.py myfile.ext http://my.tracker:6969/announce
  44. This will generate a file called myfile.ext.torrent
  45. Make sure to include the port number in the tracker url if it isn't 80.
  46. (You may also use maketorrent.py to create trackerless torrents. See
  47. the file TRACKERLESS.txt for information about trackerless operation.)
  48. This command may take a while to scan over the whole file hashing it.
  49. The /announce path is special and hard-coded into the tracker.
  50. Make sure to give the domain or ip your tracker is on instead of
  51. my.tracker.
  52. You can use either a dns name or an IP address in the tracker url.
  53. 3) associate .torrent with application/x-bittorrent on your web server
  54. The way you do this is dependent on the particular web server you're using.
  55. You must have a web server which can serve ordinary static files and is
  56. addressable from the internet at large.
  57. 4) put the newly made .torrent file on your web server
  58. Note that the file name you choose on the server must end in .torrent, so
  59. it gets associated with the right mimetype.
  60. 5) put up a static page which links to the location you uploaded to in step 4
  61. The file you uploaded in step 4 is linked to using an ordinary url.
  62. 6) start a downloader as a resume on the complete file
  63. You have to run a downloader which already has the complete file,
  64. so new downloaders have a place to get it from. Here's an example -
  65. ./bittorrent-console.py --url http://my.server/myfile.torrent --save_as myfile.ext
  66. Make sure the saveas argument points to the already complete file.
  67. If you're running the complete downloader on the same machine or LAN as
  68. the tracker, give a --ip parameter to the complete downloader. The --ip
  69. parameter can be either an IP address or DNS name.
  70. BitTorrent defaults to port 6881. If it can't use 6881, (probably because
  71. another download is happening) it tries 6882, then 6883, etc. It gives up
  72. after 6889.
  73. 7) you're done!
  74. Now you just have to get people downloading! Refer them to the page you
  75. created in step 5.
  76. BitTorrent can also publish whole directories - simply point
  77. btmaketorrent.py at the directory with files in it, they'll be
  78. published as one unit. All files in subdirectories will be included,
  79. although files and directories named 'CVS', 'core', 'Thumbs.db',
  80. 'desktop.ini' and beginning with a dot ('.') are ignored.
  81. Instructions for installation:
  82. ==============================
  83. Instructions for Unix installation are in INSTALL.unix.txt
  84. Instructions for Windows installation and creating Windows installers
  85. are in BUILD.windows.txt