PeerTube/README.md

258 lines
9.8 KiB
Markdown
Raw Normal View History

2016-07-21 10:24:18 +02:00
<h1 align="center">
PeerTube
</h1>
2015-06-09 17:41:40 +02:00
2016-07-21 10:24:18 +02:00
<h4 align="center">
Decentralized video streaming platform using P2P (BitTorrent) directly in the web browser with <a href="https://github.com/feross/webtorrent">WebTorrent</a>.
2016-07-21 10:24:18 +02:00
</h4>
2016-07-21 10:24:18 +02:00
<p align="center">
<strong>Client</strong>
2016-04-30 08:56:21 +02:00
2016-07-21 10:24:18 +02:00
<br />
2015-06-09 17:41:40 +02:00
2016-07-21 10:24:18 +02:00
<a href="https://david-dm.org/Chocobozzz/PeerTube?path=client">
<img src="https://david-dm.org/Chocobozzz/PeerTube.svg?path=client" alt="Dependency Status" />
</a>
2017-03-27 18:52:16 +02:00
<a href="https://david-dm.org/Chocobozzz/PeerTube?path=client#info=dev">
2016-07-21 10:24:18 +02:00
<img src="https://david-dm.org/Chocobozzz/PeerTube/dev-status.svg?path=client" alt="devDependency Status" />
</a>
</p>
<p align="center">
<strong>Server</strong>
<br />
<a href="https://travis-ci.org/Chocobozzz/PeerTube">
<img src="https://travis-ci.org/Chocobozzz/PeerTube.svg?branch=develop" alt="Build Status" />
2016-07-21 10:24:18 +02:00
</a>
<a href="https://david-dm.org/Chocobozzz/PeerTube">
<img src="https://david-dm.org/Chocobozzz/PeerTube.svg" alt="Dependencies Status" />
</a>
2017-03-27 18:52:16 +02:00
<a href="https://david-dm.org/Chocobozzz/PeerTube#info=dev">
2016-07-21 10:24:18 +02:00
<img src="https://david-dm.org/Chocobozzz/PeerTube/dev-status.svg" alt="devDependency Status" />
</a>
2016-07-21 11:56:38 +02:00
<a href="http://standardjs.com/">
<img src="https://img.shields.io/badge/code%20style-standard-brightgreen.svg" alt="JavaScript Style Guide" />
2016-07-21 10:24:18 +02:00
</a>
2017-01-12 19:17:12 +01:00
2016-12-14 22:47:20 +01:00
<a href="https://kiwiirc.com/client/irc.freenode.net/#peertube">
2016-12-14 22:52:57 +01:00
<img src="https://img.shields.io/badge/%23peertube-on%20freenode-brightgreen.svg" alt="PeerTube Freenode IRC" />
2016-12-14 22:47:20 +01:00
</a>
2016-07-21 10:24:18 +02:00
</p>
2016-05-11 20:01:01 +02:00
2016-07-21 11:56:38 +02:00
<br />
<p align="center">
<a href="http://peertube.cpy.re">
<img src="https://lutim.cpy.re/vC2loRww" alt="screenshot" />
</a>
</p>
## Demonstration
2016-06-05 10:49:01 +02:00
Want to see in action?
* You can directly test in your browser with this [demo server](http://peertube.cpy.re). Don't forget to use the latest version of Firefox/Chromium/(Opera?) and check your firewall configuration (for WebRTC)
* You can find [a video](https://vimeo.com/164881662 "Yes Vimeo, please don't judge me") to see how the "decentralization feature" looks like
* Experimental demo servers that share videos (they are in the same network): [peertube2](http://peertube2.cpy.re), [peertube3](http://peertube3.cpy.re). Since I do experiments with them, sometimes they might not work correctly.
## Why
We 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.
So we need to have a decentralized network (as [Diaspora](https://github.com/diaspora/diaspora) for example).
But it's not enought because one video could become famous and overload the server.
It's the reason why we need to use a P2P protocol to limit the server load.
2016-04-30 13:13:07 +02:00
Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus bittorrent) inside the web browser right now.
2015-06-09 17:41:40 +02:00
## Features
2016-04-28 19:31:08 +02:00
- [X] Frontend
2017-02-18 09:31:41 +01:00
- [X] Angular frontend
- [X] Join a network
2015-06-09 17:41:40 +02:00
- [X] Generate a RSA key
- [X] Ask for the friend list of other pods and make friend with them
- [X] Get the list of the videos owned by a pod when making friend with it
- [X] Post the list of its own videos when making friend with another pod
- [X] Quit a network
2015-06-09 17:41:40 +02:00
- [X] Upload a video
- [X] Seed the video
- [X] Send the meta data to all other friends
- [X] Remove the video
- [X] List the videos
- [X] Search a video name (local index)
2016-04-30 13:13:07 +02:00
- [X] View the video in an HTML5 page with WebTorrent
2016-06-18 16:16:30 +02:00
- [X] Manage admin account
2016-04-28 19:31:08 +02:00
- [X] Connection
- [X] Account rights (upload...)
- [X] Make the network auto sufficient (eject bad pods etc)
- [X] Validate the prototype (test PeerTube in a real world)
2017-04-09 12:13:51 +02:00
- [ ] Manage inter pod API breaks
2015-06-09 17:41:40 +02:00
- [ ] Add "DDOS" security (check if a pod don't send too many requests for example)
2016-10-01 09:57:05 +02:00
- [X] Admin panel
- [X] Stats
2016-08-23 11:45:18 +02:00
- [X] Friends list
2016-08-21 12:06:01 +02:00
- [X] Manage users (create/remove)
2016-11-20 15:27:43 +01:00
- [X] OpenGraph tags
2017-04-16 14:26:40 +02:00
- [X] Update video
- [X] Videos view count
- [X] Videos likes/dislikes
- [ ] Videos comments?
2017-04-16 14:26:40 +02:00
- [X] User registration
- [ ] User playlists
- [ ] User subscriptions (by tags, author...)
- [X] Signaling a video to the admin origin pod
2015-06-09 17:41:40 +02:00
2016-04-30 12:56:44 +02:00
## Installation
2015-06-09 17:41:40 +02:00
2017-04-09 12:13:51 +02:00
See [wiki](https://github.com/Chocobozzz/PeerTube/wiki) for complete installation commands.
### Front compatibility
2015-06-09 17:41:40 +02:00
* Chromium
* Firefox (>= 42 for MediaSource support)
2015-06-09 17:41:40 +02:00
### Dependencies
2016-10-07 14:57:58 +02:00
* **NodeJS >= 4.x**
* **npm >= 3.x**
2015-06-09 17:41:40 +02:00
* OpenSSL (cli)
2016-12-25 09:43:08 +01:00
* PostgreSQL
2017-01-12 19:17:12 +01:00
* FFmpeg
2015-06-09 17:41:40 +02:00
2016-02-14 10:29:35 +01:00
#### Debian
* Install NodeJS 4.x (actual LTS): [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)
2016-05-03 22:41:46 +02:00
* Add jessie backports to your *source.list*: http://backports.debian.org/Instructions/
2016-05-03 22:56:52 +02:00
* Run:
2016-02-14 10:29:35 +01:00
2016-05-03 22:56:52 +02:00
# apt-get update
2016-12-25 09:43:08 +01:00
# apt-get install ffmpeg postgresql-9.4 openssl
2016-09-21 22:27:04 +02:00
# npm install -g npm@3
2016-02-14 10:29:35 +01:00
2016-04-30 12:56:44 +02:00
#### Other distribution... (PR welcome)
2016-02-14 10:29:35 +01:00
2016-04-30 12:56:44 +02:00
### Sources
2015-06-09 17:41:40 +02:00
2017-01-12 19:17:12 +01:00
$ git clone -b master https://github.com/Chocobozzz/PeerTube
$ cd PeerTube
$ npm install # Or npm install --unsafe-perm for root user
2016-04-26 23:02:46 +02:00
$ npm run build
2016-04-30 12:56:44 +02:00
## Usage
2016-05-20 15:27:16 +02:00
### Production
If you want to run PeerTube for production (bad idea for now :) ):
$ cp config/production.yaml.example config/production.yaml
Then edit the `config/production.yaml` file according to your webserver configuration. Keys set in this file will override those of `config/default.yml`.
2016-05-20 15:27:16 +02:00
Finally, run the server with the `production` `NODE_ENV` variable set.
$ NODE_ENV=production npm start
2017-01-27 11:18:53 +01:00
The administrator password is automatically generated and can be found in the logs. You can set another password with:
$ NODE_ENV=production npm run reset-password -- -u root
2017-04-09 12:13:51 +02:00
**Nginx template** (reverse proxy): https://github.com/Chocobozzz/PeerTube/tree/master/support/nginx <br />
**Systemd template**: https://github.com/Chocobozzz/PeerTube/tree/master/support/systemd
2016-10-21 12:16:07 +02:00
You can check the application (CORS headers, tracker websocket...) by running:
$ NODE_ENV=production npm run check
2016-10-21 14:52:21 +02:00
### Upgrade
The following commands will upgrade the source (according to your current branch), upgrade node modules and rebuild client application:
# systemctl stop peertube
$ npm run upgrade
# systemctl start peertube
2016-12-01 22:19:34 +01:00
### Development
In this mode, the server will run requests between pods more quickly, the videos duration are limited to a few seconds and the client files are automatically compiled when we modify them:
2016-12-01 22:19:34 +01:00
$ npm run dev
**Username**: *root* <br/>
**Password**: *test*
2017-01-27 11:18:53 +01:00
2016-12-01 22:19:34 +01:00
### Test with 3 fresh nodes
$ npm run clean:server:test
$ npm run play
Then you will can access to the three nodes at `http://localhost:900{1,2,3}` with the `root` as username and `test{1,2,3}` for the password. 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 :)
2016-04-30 12:56:44 +02:00
### Other commands
To print all available command run:
$ npm run help
## Dockerfile
2015-06-09 17:41:40 +02:00
2015-11-03 09:05:03 +01:00
You 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.
2015-06-09 17:41:40 +02:00
2016-07-22 11:45:48 +02:00
## Contributing
See the [contributing guide](https://github.com/Chocobozzz/PeerTube/blob/master/.github/CONTRIBUTING.md).
See the [server code documentation](https://github.com/Chocobozzz/PeerTube/blob/master/support/doc/server/code.md).
2016-12-01 22:19:34 +01:00
See the [client code documentation](https://github.com/Chocobozzz/PeerTube/blob/master/support/doc/client/code.md).
2016-07-22 11:45:48 +02:00
2015-06-09 17:41:40 +02:00
## Architecture
2015-10-29 23:18:17 +01:00
See [ARCHITECTURE.md](https://github.com/Chocobozzz/PeerTube/blob/master/ARCHITECTURE.md) for a more detailed explication.
2015-06-09 17:41:40 +02:00
### Backend
2016-07-21 10:37:29 +02:00
* The backend is a REST API
* Servers communicate with each others through it
* A network is composed by servers that communicate between them
* Each server of a network has a list of all other servers of this network
* When a new installed server wants to join a network, it just has to get the servers list through a server that is already in the network and tell "Hi I'm new in the network, communicate with me and share me your servers list please". Then the server will "make friend" with each server of this list
2015-06-09 17:41:40 +02:00
* Each server has its own users who query it (search videos, where the torrent URI of this specific video is...)
2016-07-22 11:53:55 +02:00
* If a user upload a video, the server seeds it and sends the video informations (name, short description, torrent URI...) to each server of the network
2015-06-09 17:41:40 +02:00
* Each server has a RSA key to encrypt and sign communications with other servers
* A server is a tracker responsible for all the videos uploaded in it
* Even if nobody watches a video, it is seeded by the server (throught [WebSeed protocol](http://www.bittorrent.org/beps/bep_0019.html)) where the video was uploaded
2015-06-09 17:41:40 +02:00
* A network can live and evolve by expelling bad pod (with too many downtimes for example)
See the ARCHITECTURE.md for more informations. Do not hesitate to give your opinion :)
Here are some simple schemes:
2016-07-21 10:24:18 +02:00
<p align="center">
<img src="https://lutim.cpy.re/isWwz8tt" alt="Decentralized" />
2016-07-21 10:24:18 +02:00
<img src="https://lutim.cpy.re/VLheltQk" alt="Watch a video" />
2015-06-09 17:41:40 +02:00
<img src="https://lutim.cpy.re/worHQwKv" alt="Watch a P2P video" />
2015-06-09 17:41:40 +02:00
<img src="https://lutim.cpy.re/MyeS4q1g" alt="Join a network" />
2015-06-09 17:41:40 +02:00
2016-12-24 17:12:40 +01:00
<img src="https://lutim.cpy.re/PqpTTzdP" alt="Many networks" />
2015-06-09 17:41:40 +02:00
2016-07-21 10:24:18 +02:00
</p>
2015-06-09 17:41:40 +02:00
### Frontend
2016-07-21 11:56:38 +02:00
There already is a frontend (Angular 2) but the backend is a REST API so anybody can build a frontend (Web application, desktop application...).
The backend uses BitTorrent protocol, so users could use their favorite BitTorrent client to download/play the video with its torrent URI.