diff options
-rw-r--r-- | FAQ.md | 6 | ||||
-rw-r--r-- | README.md | 10 |
2 files changed, 8 insertions, 8 deletions
@@ -1,6 +1,6 @@ | |||
1 | # FAQ | 1 | # FAQ |
2 | 2 | ||
3 | ## If nobody watch a video, is it seeded? | 3 | ## If nobody watches a video, is it seeded? |
4 | 4 | ||
5 | Yes, the origin server always seeds videos uploaded on it through [Webseed](http://www.bittorrent.org/beps/bep_0019.html). | 5 | Yes, the origin server always seeds videos uploaded on it through [Webseed](http://www.bittorrent.org/beps/bep_0019.html). |
6 | 6 | ||
@@ -12,7 +12,7 @@ It is a BitTorrent extension that allow a server to seed a file through HTTP. It | |||
12 | 12 | ||
13 | ## If a client requests each chunk of a video through HTTP, the server be overloaded! | 13 | ## If a client requests each chunk of a video through HTTP, the server be overloaded! |
14 | 14 | ||
15 | Not really. Reverse proxy like Nginx handle very well requests of static files. In my tests it can send chunks at 10MB/s without consuming more than 5% of CPU on a very small VPS. | 15 | Not really. Reverse proxies like Nginx handle very well requests of static files. In my tests it can send chunks at 10MB/s without consuming more than 5% of CPU on a very small VPS. |
16 | 16 | ||
17 | 17 | ||
18 | ## An index of all videos of the network won't be too large for small servers? | 18 | ## An index of all videos of the network won't be too large for small servers? |
@@ -25,7 +25,7 @@ No, 1000000 videos will represent around 2GB on PostgreSQL. It is acceptable for | |||
25 | WEBM, MP4 or OGV videos. | 25 | WEBM, MP4 or OGV videos. |
26 | 26 | ||
27 | 27 | ||
28 | ## I want to change my host or move to HTTPS, how can I do? | 28 | ## I want to change my host or move to HTTPS, how can I do that? |
29 | 29 | ||
30 | If you already have friends you need to quit them. | 30 | If you already have friends you need to quit them. |
31 | Then, update your configuration and run `NODE_ENV=production npm run update-host` to update the torrent files. | 31 | Then, update your configuration and run `NODE_ENV=production npm run update-host` to update the torrent files. |
@@ -66,10 +66,10 @@ Want to see in action? | |||
66 | 66 | ||
67 | ## Why | 67 | ## Why |
68 | 68 | ||
69 | 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. | 69 | 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. |
70 | 70 | ||
71 | So we need to have a decentralized network (as [Diaspora](https://github.com/diaspora/diaspora) for example). | 71 | So we need to have a decentralized network (as [Diaspora](https://github.com/diaspora/diaspora) for example). |
72 | But it's not enought because one video could become famous and overload the server. | 72 | But it's not enough because one video could become famous and overload the server. |
73 | It's the reason why we need to use a P2P protocol to limit the server load. | 73 | It's the reason why we need to use a P2P protocol to limit the server load. |
74 | Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus bittorrent) inside the web browser right now. | 74 | Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus bittorrent) inside the web browser right now. |
75 | 75 | ||
@@ -194,9 +194,9 @@ The following commands will upgrade the source (according to your current branch | |||
194 | 194 | ||
195 | ### Development | 195 | ### Development |
196 | 196 | ||
197 | In this mode, the server will run requests between pods more quickly, the videos duration are limited to a few seconds. | 197 | In this mode, the server will run requests between pods more quickly, the video durations are limited to a few seconds. |
198 | 198 | ||
199 | To develop on the server side (server files are automatically compiled when we modify them and the server restarts automatically too): | 199 | To develop on the server-side (server files are automatically compiled when we modify them and the server restarts automatically too): |
200 | 200 | ||
201 | $ npm run dev:server | 201 | $ npm run dev:server |
202 | 202 | ||
@@ -217,7 +217,7 @@ The API will listen on `localhost:9000` and the frontend on `localhost:3000` (wi | |||
217 | $ npm run clean:server:test | 217 | $ npm run clean:server:test |
218 | $ npm run play | 218 | $ npm run play |
219 | 219 | ||
220 | 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 :) | 220 | 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 :) |
221 | 221 | ||
222 | ### Other commands | 222 | ### Other commands |
223 | 223 | ||