PeerTube/.github/CONTRIBUTING.md

107 lines
3.2 KiB
Markdown
Raw Normal View History

2016-07-22 11:45:29 +02:00
# Welcome to the contributing guide for PeerTube
2018-01-12 18:07:41 +01:00
Interesting in contributing? Awesome!
2016-07-22 11:45:29 +02:00
**Quick Links:**
* [Give your feedback](#give-your-feedback)
* [Write documentation](#write-documentation)
2018-01-12 18:07:41 +01:00
* [Develop](#develop)
2016-07-22 11:45:29 +02:00
## Give your feedback
You don't need to know how to code to start contributing to PeerTube! Other
contributions are very valuable too, among which: you can test the software and
report bugs, you can give feedback on potential bugs, features that you are
2018-01-12 18:07:41 +01:00
interested in, user interface, design, decentralized architecture...
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
## Write documentation
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
You can help to write the documentation of the REST API, code, architecture,
2018-01-24 12:02:38 +01:00
demonstrations.
For the REST API you can see the documentation in [/support/doc/api](/support/doc/api) directory.
Then, you can just open the `openapi.yaml` file in a special editor like [http://editor.swagger.io/](http://editor.swagger.io/) to easily see and edit the documentation.
Some hints:
* Routes are defined in [/server/controllers/](/server/controllers/) directory
* Parameters validators are defined in [/server/middlewares/validators](/server/middlewares/validators) directory
* Models sent/received by the controllers are defined in [/shared/models](/shared/models) directory
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
## Develop
2016-07-22 11:45:29 +02:00
Don't hesitate to talk about features you want to develop by creating an issue
before you start working on them :).
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
### Prerequisites
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
First, make sure that you have followed
[the steps](/support/doc/dependencies.md)
to install the dependencies.
2018-01-12 18:07:41 +01:00
Then clone the sources and install node modules:
2018-01-12 18:55:45 +01:00
```
2018-01-12 18:07:41 +01:00
$ git clone -b master https://github.com/Chocobozzz/PeerTube
$ cd PeerTube
$ yarn install --pure-lockfile
```
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`
and a postgres user called `peertube` with password `peertube`:
2018-01-12 18:55:45 +01:00
```
2018-01-12 18:07:41 +01:00
# sudo -u postgres createuser -P peertube
Enter password for new role: peertube
# sudo -u postgres createdb -O peertube peertube_dev
```
2018-01-12 18:07:41 +01:00
In dev mode, administrator username is **root** and password is **test**.
### Server side
2018-01-12 18:07:41 +01:00
You can find a documentation of the server code/architecture [here](/support/doc/development/server/code.md).
To develop on the server-side:
2018-01-12 18:55:45 +01:00
```
2018-01-12 18:07:41 +01:00
$ 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
2018-01-12 18:07:41 +01:00
restart. Server is in `TEST` mode so it will run requests between instances more quickly.
### Client side
2018-01-12 18:07:41 +01:00
You can find a documentation of the server code/architecture
[here](/support/doc/development/client/code.md).
To develop on the client side:
2018-01-12 18:55:45 +01:00
```
2018-01-12 18:07:41 +01:00
$ npm run dev:client
```
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.
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
### Test federation
2016-12-01 22:16:38 +01:00
2018-01-12 18:07:41 +01:00
This will run 3 nodes:
2016-07-22 11:45:29 +02:00
2018-01-12 18:55:45 +01:00
```
2018-01-12 18:07:41 +01:00
$ npm run clean:server:test
$ npm run play
```
2016-07-22 11:45:29 +02:00
2018-01-12 18:07:41 +01:00
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.