PeerTube

PeerTube

Decentralized video streaming platform using P2P (BitTorrent) directly in the web browser with WebTorrent.

PeerTube is sponsored by Framasoft, a non-profit that promotes, spreads and develops free-libre software. If you want to support this project, please consider donating them.

Client

Server

Demonstration

Want to see in action?

• Demo server
• Video to see how the "decentralization feature" looks like
• Experimental demo servers that share videos (they are in the same network): peertube2, peertube3. 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 enough money to pay bandwidth and video storage of its server.

So we need to have a decentralized network (as Diaspora for example). But it's not enough 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. Thanks to WebTorrent, we can make P2P (thus bittorrent) inside the web browser right now.

Features

• [X] Frontend
  • [X] Angular frontend
• [X] Join a network
  • [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
• [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)
• [X] View the video in an HTML5 page with WebTorrent
• [X] Manage admin account
  • [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)
• Manage inter pod API breaks
• Add "DDOS" security (check if a pod don't send too many requests for example)
• [X] Admin panel
  • [X] Stats
  • [X] Friends list
  • [X] Manage users (create/remove)
• [X] OpenGraph tags
• [X] OEmbed
• [X] Update video
• [X] Videos view counter
• [X] Videos likes/dislikes
• [X] Transcoding to different definitions
• [X] Download file/torrent
• [X] User video bytes quota
• [X] User channels
• [X] NSFW warnings/settings
• [X] Video description in markdown
• [X] User roles (administrator, moderator)
• [X] User registration
• [X] Video privacy settings (public, unlisted or private)
• [X] Signaling a video to the admin origin pod
• Videos comments
• User playlist
• User subscriptions (by tags, author...)

Installation

See wiki for complete installation commands.

Front compatibility

• Chromium
• Firefox (>= 42 for MediaSource support)

Dependencies

• NodeJS >= 6.x
• npm >= 3.x
• yarn
• OpenSSL (cli)
• PostgreSQL
• FFmpeg

Debian

• Install NodeJS 6.x (actual LTS): https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions
• Install yarn: https://yarnpkg.com/en/docs/install
• Add jessie backports to your source.list: http://backports.debian.org/Instructions/

• Run:

  # apt-get update
  # apt-get install ffmpeg postgresql-9.4 openssl
  

Other distribution... (PR welcome)

Sources

$ git clone -b master https://github.com/Chocobozzz/PeerTube
$ cd PeerTube
$ yarn install
$ npm run build

Usage

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.

Finally, run the server with the production NODE_ENV variable set.

$ NODE_ENV=production npm start

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

Nginx template (reverse proxy): https://github.com/Chocobozzz/PeerTube/tree/master/support/nginx
Systemd template: https://github.com/Chocobozzz/PeerTube/tree/master/support/systemd

You can check the application (CORS headers, tracker websocket...) by running:

$ NODE_ENV=production npm run check

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-peertube
# systemctl start peertube

Development

In this mode, the server will run requests between pods more quickly, the video durations are limited to a few seconds.

To develop on the server-side (server files are automatically compiled when we modify them and the server restarts automatically too):

$ npm run dev:server

The server (with the client) will listen on localhost:9000.

To develop on the client side (client files are automatically compiled when we modify them):

$ npm run dev:client

The API will listen on localhost:9000 and the frontend on localhost:3000 (with hot module replacement, you don't need to refresh the web browser).

Username: root
Password: test

Test with 3 fresh nodes

$ npm run clean:server:test
$ npm run play

Then you will get 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 :)

Other commands

To print all available command run:

$ npm run help

Dockerfile

You can test it inside Docker with the PeerTube-Docker repository. Moreover it can help you to check how to create an environment with the required dependencies for PeerTube on a GNU/Linux distribution.

Contributing

See the contributing guide.

See the server code documentation.

See the client code documentation.

Architecture

See ARCHITECTURE.md for a more detailed explication.

Backend

• 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
  • Each server has its own users who query it (search videos, where the torrent URI of this specific video is...)
  • If a user upload a video, the server seeds it and sends the video information (name, short description, torrent URI...) to each server of the network
  • 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 (through WebSeed protocol) where the video was uploaded
• A network can live and evolve by expelling bad pod (with too many downtime for example)

See the ARCHITECTURE.md for more information. Do not hesitate to give your opinion :)

Here are some simple schemes:

Frontend

There already is a frontend (Angular) 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.