X-Git-Url: https://git.immae.eu/?a=blobdiff_plain;f=.github%2FCONTRIBUTING.md;h=6d095cc474ded3ae74710eed53b478a2e84d343c;hb=3f6b6a565dc98a658ec9d8f697252788c0faa46d;hp=c9988bfeab3348037550932d9721f913d283b7e5;hpb=c263f3b425354cb0114d8fc22b8c4a96c3865c0b;p=github%2FChocobozzz%2FPeerTube.git diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index c9988bfea..6d095cc47 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -4,11 +4,17 @@ Interesting in contributing? Awesome! **Quick Links:** + * [Translate](#translate) * [Give your feedback](#give-your-feedback) * [Write documentation](#write-documentation) * [Develop](#develop) +## Translate + +You can help us to translate the PeerTube interface to many languages! See [the documentation](/support/doc/translation.md) to know how. + + ## Give your feedback You don't need to know how to code to start contributing to PeerTube! Other @@ -50,6 +56,10 @@ $ cd PeerTube $ yarn install --pure-lockfile ``` +Note that development is done on the `develop` branch. If you want to hack on +Peertube, you should switch to that branch. Also note that you have to repeat +the `yarn install --pure-lockfile` command. + Then, create a postgres database and user with the values set in the `config/default.yaml` file. For instance, if you do not change the values there, the following commands would create a new database called `peertube_dev` @@ -61,6 +71,13 @@ Enter password for new role: peertube # sudo -u postgres createdb -O peertube peertube_dev ``` +Then enable extensions PeerTube needs: + +``` +$ sudo -u postgres psql -c "CREATE EXTENSION pg_trgm;" peertube_dev +$ sudo -u postgres psql -c "CREATE EXTENSION unaccent;" peertube_dev +``` + In dev mode, administrator username is **root** and password is **test**. ### Server side @@ -75,7 +92,7 @@ $ npm run dev:server Then, the server will listen on `localhost:9000`. When server source files change, these are automatically recompiled and the server will automatically -restart. Server is in `TEST` mode so it will run requests between instances more quickly. +restart. ### Client side @@ -93,14 +110,67 @@ The API will listen on `localhost:9000` and the frontend on `localhost:3000`. Client files are automatically compiled on change, and the web browser will reload them automatically thanks to hot module replacement. -### Test federation +### Client and server side -This will run 3 nodes: +The API will listen on `localhost:9000` and the frontend on `localhost:3000`. +File changes are automatically recompiled, injected in the web browser (no need to refresh manually) +and the web server is automatically restarted. ``` +$ npm run dev +``` + +### Federation + +Create a PostgreSQL user **with the same name as your username** in order to avoid using the *postgres* user. +Then, we can create the databases (if they don't already exist): + +``` +$ sudo -u postgres createuser you_username --createdb +$ createdb -O peertube peertube_test{1,2,3} +``` + +Build the application and flush the old tests data: + +``` +$ npm run build $ npm run clean:server:test +``` + +This will run 3 nodes: + +``` $ 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. + +Instance configurations are in `config/test-{1,2,3}.yaml`. + +### Unit tests + +Create a PostgreSQL user **with the same name as your username** in order to avoid using the *postgres* user. + +Then, we can create the databases (if they don't already exist): + +``` +$ sudo -u postgres createuser you_username --createdb --superuser +$ createdb -O peertube peertube_test{1,2,3,4,5,6} +``` + +Build the application and run the unit/integration tests: + +``` +$ npm run build +$ npm test +``` + +If you just want to run 1 test: + +``` +$ npm run mocha -- --exit --require ts-node/register/type-check --bail server/tests/api/index.ts +``` + +Instance configurations are in `config/test-{1,2,3,4,5,6}.yaml`. +Note that only instance 2 has transcoding enabled. \ No newline at end of file