Fix spelling (#126)
This commit is contained in:
parent
8114c5d800
commit
343ad675f2
6
FAQ.md
6
FAQ.md
|
@ -1,6 +1,6 @@
|
||||||
# FAQ
|
# FAQ
|
||||||
|
|
||||||
## If nobody watch a video, is it seeded?
|
## If nobody watches a video, is it seeded?
|
||||||
|
|
||||||
Yes, the origin server always seeds videos uploaded on it through [Webseed](http://www.bittorrent.org/beps/bep_0019.html).
|
Yes, the origin server always seeds videos uploaded on it through [Webseed](http://www.bittorrent.org/beps/bep_0019.html).
|
||||||
|
|
||||||
|
@ -12,7 +12,7 @@ It is a BitTorrent extension that allow a server to seed a file through HTTP. It
|
||||||
|
|
||||||
## If a client requests each chunk of a video through HTTP, the server be overloaded!
|
## If a client requests each chunk of a video through HTTP, the server be overloaded!
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
|
||||||
## An index of all videos of the network won't be too large for small servers?
|
## 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
|
||||||
WEBM, MP4 or OGV videos.
|
WEBM, MP4 or OGV videos.
|
||||||
|
|
||||||
|
|
||||||
## I want to change my host or move to HTTPS, how can I do?
|
## I want to change my host or move to HTTPS, how can I do that?
|
||||||
|
|
||||||
If you already have friends you need to quit them.
|
If you already have friends you need to quit them.
|
||||||
Then, update your configuration and run `NODE_ENV=production npm run update-host` to update the torrent files.
|
Then, update your configuration and run `NODE_ENV=production npm run update-host` to update the torrent files.
|
||||||
|
|
10
README.md
10
README.md
|
@ -66,10 +66,10 @@ Want to see in action?
|
||||||
|
|
||||||
## Why
|
## 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.
|
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](https://github.com/diaspora/diaspora) for example).
|
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.
|
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.
|
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.
|
Thanks to [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus bittorrent) inside the web browser right now.
|
||||||
|
|
||||||
|
@ -194,9 +194,9 @@ The following commands will upgrade the source (according to your current branch
|
||||||
|
|
||||||
### Development
|
### Development
|
||||||
|
|
||||||
In this mode, the server will run requests between pods more quickly, the videos duration are limited to a few seconds.
|
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):
|
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
|
$ npm run dev:server
|
||||||
|
|
||||||
|
@ -217,7 +217,7 @@ The API will listen on `localhost:9000` and the frontend on `localhost:3000` (wi
|
||||||
$ npm run clean:server:test
|
$ npm run clean:server:test
|
||||||
$ npm run play
|
$ 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 :)
|
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
|
### Other commands
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue