]> git.immae.eu Git - github/Chocobozzz/PeerTube.git/blame - README.md
Oup's, travis is based on ubuntu precise
[github/Chocobozzz/PeerTube.git] / README.md
CommitLineData
d148f3b9 1# PeerTube
8c308c2b 2
191ce958 3*Server*
81b005a7 4
88c8d458 5[![Build Status](https://travis-ci.org/Chocobozzz/PeerTube.svg?branch=master)](https://travis-ci.org/Chocobozzz/PeerTube)
dcc700d2 6[![Dependencies Status](https://david-dm.org/Chocobozzz/PeerTube.svg)](https://david-dm.org/Chocobozzz/PeerTube)
9e9b8a0f 7[![devDependency Status](https://david-dm.org/Chocobozzz/PeerTube/dev-status.svg)](https://david-dm.org/Chocobozzz/PeerTube#info=devDependencies)
3dca0e6e 8[![Code climate](https://codeclimate.com/github/Chocobozzz/PeerTube/badges/gpa.svg)](https://codeclimate.com/github/Chocobozzz/PeerTube)
88c8d458 9
191ce958 10*Client*
81b005a7 11
191ce958
C
12[![Dependency Status](https://david-dm.org/Chocobozzz/PeerTube.svg?path=client)](https://david-dm.org/Chocobozzz/PeerTube?path=client)
13[![devDependency Status](https://david-dm.org/Chocobozzz/PeerTube/dev-status.svg?path=client)](https://david-dm.org/Chocobozzz/PeerTube?path=client#info=devDependencies)
14
2eb5a041 15Prototype of a decentralized video streaming platform using P2P (bittorrent) directly in the web browser with [WebTorrent](https://github.com/feross/webtorrent).
8c308c2b
C
16
17[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)
18
15e3cdaa
C
19![screenshot](https://lutim.cpy.re/vC2loRww)
20
21## Demonstration
22
23PeerTube is not ready for production yet, but you can find [a video](https://vimeo.com/164881662 "Yes Vimeo, please don't judge me") to see how it looks like.
24
88c8d458
C
25## Why
26
27We can't build a FOSS video streaming alternatives to YouTube, Dailymotion, Vimeo... with a centralized software. One organization alone cannot have enought money to pay bandwith and video storage of its server.
28
29So we need to have a decentralized network (as [Diaspora](https://github.com/diaspora/diaspora) for example).
30But it's not enought because one video could become famous and overload the server.
31It's the reason why we need to use a P2P protocol to limit the server load.
2eb5a041 32Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus bittorrent) inside the web browser right now.
88c8d458 33
8c308c2b
C
34## Features
35
da817527 36- [X] Frontend
e9f2c1ac
C
37 - [X] ~~Simple frontend (All elements are generated by jQuery)~~
38 - [X] Angular 2 frontend
45239549 39- [X] Join a network
8c308c2b
C
40 - [X] Generate a RSA key
41 - [X] Ask for the friend list of other pods and make friend with them
45239549
C
42 - [X] Get the list of the videos owned by a pod when making friend with it
43 - [X] Post the list of its own videos when making friend with another pod
44- [X] Quit a network
8c308c2b
C
45- [X] Upload a video
46 - [X] Seed the video
47 - [X] Send the meta data to all other friends
48- [X] Remove the video
49- [X] List the videos
50- [X] Search a video name (local index)
2eb5a041 51- [X] View the video in an HTML5 page with WebTorrent
8c308c2b
C
52- [ ] Manage user accounts
53 - [ ] Inscription
da817527
C
54 - [X] Connection
55 - [X] Account rights (upload...)
3bcb78b3 56- [X] Make the network auto sufficient (eject bad pods etc)
8c308c2b
C
57- [ ] Manage API breaks
58- [ ] Add "DDOS" security (check if a pod don't send too many requests for example)
59
8c308c2b 60
94171ec5 61## Installation
8c308c2b 62
88c8d458 63### Front compatibility
8c308c2b 64
88c8d458
C
65 * Chromium
66 * Firefox (>= 42 for MediaSource support)
8c308c2b
C
67
68### Dependencies
69
86435b9b 70 * **NodeJS >= 4.2**
8c308c2b
C
71 * OpenSSL (cli)
72 * MongoDB
3a8a8b51 73 * ffmpeg xvfb-run libgtk2.0-0 libgconf-2-4 libnss3 libasound2 libxtst6 libxss1 libnotify-bin (for electron)
8c308c2b 74
c35ae59d
C
75#### Debian
76
3a8a8b51
C
77 * Install NodeJS 4.2: [https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions](https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions)
78 * Add jessie backports to your *source.list*: http://backports.debian.org/Instructions/
2e2b64c5 79 * Run:
c35ae59d 80
2e2b64c5
BF
81 # apt-get update
82 # apt-get install ffmpeg mongodb openssl xvfb curl sudo git build-essential libgtk2.0-0 libgconf-2-4 libnss3 libasound2 libxtst6 libxss1 libnotify-bin
83 # npm install -g electron-prebuilt
c35ae59d 84
94171ec5
C
85#### Other distribution... (PR welcome)
86
c35ae59d 87
94171ec5 88### Sources
8c308c2b
C
89
90 $ git clone https://github.com/Chocobozzz/PeerTube
d148f3b9 91 $ cd PeerTube
8c308c2b 92 $ npm install
26939223 93 $ npm run build
94171ec5
C
94
95## Usage
96
97### Run the server
98
8c308c2b
C
99 $ npm start
100
9e0e8506 101### Test with 3 fresh nodes
88c8d458 102
94171ec5
C
103 $ npm run clean:server:test
104 $ npm run play
8c308c2b 105
c35ae59d 106Then you will can access to the three nodes at `http://localhost:900{1,2,3}`. If you call "make friends" on `http://localhost:9002`, the pod 2 and 3 will become friends. Then if you call "make friends" on `http://localhost:9001` it will become friend with the pod 2 and 3 (check the configuration files). Then the pod will communicate with each others. If you add a video on the pod 3 you'll can see it on the pod 1 and 2 :)
8c308c2b 107
94171ec5
C
108### Other commands
109
110To print all available command run:
111
112 $ npm run help
113
114## Dockerfile
8c308c2b 115
a6fa7ac1 116You can test it inside Docker with the [PeerTube-Docker repository](https://github.com/Chocobozzz/PeerTube-Docker). Moreover it can help you to check how to create an environment with the required dependencies for PeerTube on a GNU/Linux distribution.
8c308c2b
C
117
118## Architecture
119
241abd69
BF
120See [ARCHITECTURE.md](https://github.com/Chocobozzz/PeerTube/blob/master/ARCHITECTURE.md) for a more detailed explication.
121
8c308c2b
C
122### Backend
123
124 * The backend whould be a REST API
125 * Servers would communicate with each others with it
126 * Each server of a network has a list of all other servers of the network
127 * When a new installed server wants to join a network, it just has to get the list of the servers via one server and tell them "Hi I'm new in the network, communicate with me too please"
128 * Each server has its own users who query it (search videos, where the torrent URI of this specific video is...)
129 * Server begins to seed and sends to the other servers of the network the video information (name, short description, torrent URI) of a new uploaded video
130 * Each server has a RSA key to encrypt and sign communications with other servers
131 * A server is a tracker responsible for all the videos uploaded in it
132 * Even if nobody watches a video, it is seeded by the server where the video was uploaded
133 * A server would run webtorrent-hybrid to be a bridge with webrtc/standard bittorrent protocol
134 * A network can live and evolve by expelling bad pod (with too many downtimes for example)
135
136See the ARCHITECTURE.md for more informations. Do not hesitate to give your opinion :)
137
138Here are some simple schemes:
139
15e3cdaa 140![Decentralized](https://lutim.cpy.re/Q7mnNdJP)
8c308c2b 141
15e3cdaa 142![Watch a video](https://lutim.cpy.re/0riSzAp1)
8c308c2b 143
15e3cdaa 144![Watch a video P2P](https://lutim.cpy.re/OzMSOtxG)
8c308c2b 145
15e3cdaa 146![Join a network](https://lutim.cpy.re/uVjNNRa9)
8c308c2b 147
15e3cdaa 148![Many networks](https://lutim.cpy.re/udTMqcb0)
8c308c2b
C
149
150### Frontend
151
152There would be a simple frontend (Bootstrap, AngularJS) but since the backend is a REST API anybody could build a frontend (Web application, desktop application...).
88c8d458 153The backend uses bittorrent protocol, so users could use their favorite bittorrent client to download/play the video after having its torrent URI.