X-Git-Url: https://git.immae.eu/?a=blobdiff_plain;f=README.md;h=88eac088a1471f5c91a11acab7eafd3692cd5b4d;hb=e1a540b5fa14b0fafa63f99e344927b10fdbee00;hp=efacfc7410b981336d718d01448502474728ca77;hpb=900f0d2b3cc5035568ffa0853101a12c6abcffdc;p=github%2FChocobozzz%2FPeerTube.git diff --git a/README.md b/README.md index efacfc741..88eac088a 100644 --- a/README.md +++ b/README.md @@ -3,9 +3,15 @@
Client
@@ -15,9 +21,13 @@ Prototype of a decentralized video streaming platform using P2P (bittorrent) dir
-
+
+
+
+
+
@@ -26,215 +36,152 @@ Prototype of a decentralized video streaming platform using P2P (bittorrent) dir
-
+
-
+
-
-
-
-
+
+
+
+
+ Website | + Instances list + +
+ ## Demonstration -Want to see in action? +Want to see it 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. + * Demonstration servers: + * [peertube.cpy.re](http://peertube.cpy.re) + * [peertube2.cpy.re](http://peertube2.cpy.re) + * [peertube3.cpy.re](http://peertube3.cpy.re) + * [Video](https://peertube.cpy.re/videos/watch/f78a97f8-a142-4ce1-a5bd-154bf9386504) + to see what the "decentralization feature" looks like + * [Video](https://peertube.cpy.re/videos/watch/da2b08d4-a242-4170-b32a-4ec8cbdca701) to see + the communication between PeerTube and [Mastodon](https://github.com/tootsuite/mastodon) ## 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. -Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus bittorrent) inside the web browser right now. - -## Features - -- [X] Frontend - - [X] ~~Simple frontend (All elements are generated by jQuery)~~ - - [X] Angular 2 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) -- [ ] Validate the prototype (test PeerTube in a real world with many pods and videos) -- [ ] Manage 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 -- [ ] User playlists -- [ ] User subscriptions (by tags, author...) -- [ ] Signaling a video to the admin pod - -## Installation - -### Front compatibility - - * Chromium - * Firefox (>= 42 for MediaSource support) - -### Dependencies - - * **NodeJS >= 4.x** - * **npm >= 3.x** - * OpenSSL (cli) - * MongoDB - * ffmpeg - -#### 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) - * Add jessie backports to your *source.list*: http://backports.debian.org/Instructions/ - * Run: - - # apt-get update - # apt-get install ffmpeg mongodb openssl - # npm install -g npm@3 - -#### Other distribution... (PR welcome) - - -### Sources - - $ git clone https://github.com/Chocobozzz/PeerTube - $ cd PeerTube - $ npm install # Or npm install --unsafe-perm for root user - $ npm run build +We can't build a FOSS video streaming alternatives to YouTube, Dailymotion, +Vimeo... with a centralized software. One organization alone may not have +enough money to pay for bandwidth and video storage of its servers. -## Usage +So we need to have a decentralized network of servers seeding videos (as +[Diaspora](https://github.com/diaspora/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](https://github.com/feross/webtorrent), we can make P2P (thus +BitTorrent) inside the web browser, as of today. -### Development +## Dependencies - $ npm run dev - -### 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 :) - -### 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. - -Finally, run the server with the `production` `NODE_ENV` variable set. - - $ NODE_ENV=production npm start - -**Nginx template** (reverse proxy): https://github.com/Chocobozzz/PeerTube/tree/master/support/nginx - -**Systemd template**: https://github.com/Chocobozzz/PeerTube/tree/master/support/systemd + * nginx + * PostgreSQL + * Redis + * **NodeJS >= 8.x** + * yarn + * OpenSSL (cli) + * **FFmpeg >= 3.x** -You can check the application (CORS headers, tracker websocket...) by running: +## Run using Docker - $ NODE_ENV=production npm run check +See the [docker guide](/support/doc/docker.md) -### Upgrade +## Production -The following commands will upgrade the source (according to your current branch), upgrade node modules and rebuild client application: +See the [production guide](/support/doc/production.md). - # systemctl stop peertube - $ npm run upgrade - # systemctl start peertube +## Contributing/Test -### Other commands +See the [contributing +guide](/.github/CONTRIBUTING.md) +to see how to test or contribute to PeerTube. Spoiler alert: you don't need to be a +coder to help! -To print all available command run: +## API REST documentation - $ npm run help +Quick Start: [/support/doc/api/quickstart.md](/support/doc/api/quickstart.md) -## Dockerfile +Endpoints documentation: -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. + * HTML version: [/support/doc/api/html/index.html](https://htmlpreview.github.io/?https://github.com/Chocobozzz/PeerTube/blob/develop/support/doc/api/html/index.html) + * Swagger/OpenAPI schema: [/support/doc/api/openapi.yaml](/support/doc/api/openapi.yaml) -## Contributing +## Tools -See the [contributing guide](https://github.com/Chocobozzz/PeerTube/blob/master/.github/CONTRIBUTING.md). + * [Import videos (YouTube, Dailymotion, Vimeo...)](/support/doc/tools.md) + * [Upload videos from the CLI](/support/doc/tools.md) -See the [server code documentation](https://github.com/Chocobozzz/PeerTube/blob/master/support/doc/server/code.md). +## FAQ +If you have a question, please try to find the answer in the [FAQ](/FAQ.md) first. ## Architecture -See [ARCHITECTURE.md](https://github.com/Chocobozzz/PeerTube/blob/master/ARCHITECTURE.md) for a more detailed explication. +See [ARCHITECTURE.md](/ARCHITECTURE.md) for a more detailed explanation. ### 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 informations (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 (throught [WebSeed protocol](http://www.bittorrent.org/beps/bep_0019.html)) where the video was uploaded - * 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 :) + * The backend is a REST API. + * Servers communicate with each others with [Activity + Pub](https://www.w3.org/TR/activitypub/). + * Each server has its own users who query it (search videos, query where the + torrent URI of this specific video is...). + * If a user uploads a video, the server seeds it and sends its followers some + metadata (name, short description, torrent URI...). + * 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](http://www.bittorrent.org/beps/bep_0019.html)) where the + video was uploaded. Here are some simple schemes:
-
+
+
+
-
+
-
+