Add telemetry to Taiga

This commit is contained in:
Yamila Moreno 2020-12-09 21:04:08 +01:00 committed by David Barragán Merino
parent a6c56b6d6e
commit 1ae321e530
2 changed files with 18 additions and 7 deletions

View File

@ -31,13 +31,13 @@ This vars will be used to connect to the Taiga database.
**Important**: these vars should have the same values as `taiga-db` service vars. **Important**: these vars should have the same values as `taiga-db` service vars.
##### `POSTGRES_HOST` ##### `POSTGRES_HOST`
Where the database is set. By default, it's meant to be in the same host as the database service so it uses internal docker names. Where the database is set. By default, it's meant to be in the same host as the database service so it uses internal docker names.
#### Taiga settings #### Taiga settings
##### `TAIGA_SECRET_KEY` ##### `TAIGA_SECRET_KEY`
Is the secret key of Taiga. Should be the same as this var in `taiga-events` and `taiga-async` Is the secret key of Taiga. Should be the same as this var in `taiga-events` and `taiga-async`
@ -45,9 +45,17 @@ Is the secret key of Taiga. Should be the same as this var in `taiga-events` and
Should have the url where this is served: https[://]taiga.mycompany.com Should have the url where this is served: https[://]taiga.mycompany.com
#### Telemetry Settings
Telemetry anonymous data is collected in order to learn about the use of Taiga and improve the platform based on real scenarios.
##### `ENABLE_TELEMETRY`
You can opt out by setting this variable to "False". By default is "True".
#### Email Settings #### Email Settings
By default, email is configured with the *console* backend, which means that the emails will be shown in the stdout.<br> By default, email is configured with the *console* backend, which means that the emails will be shown in the stdout.
##### `ENABLE_EMAIL` ##### `ENABLE_EMAIL`
@ -96,14 +104,13 @@ Is the secret erlang cookie.
This vars will be used to connect to rabbitmq. This vars will be used to connect to rabbitmq.
### taiga-front ### taiga-front
##### `TAIGA_URL` ##### `TAIGA_URL`
Where this Taiga instance should be served. It should be the same as `TAIGA_SITES_SCHEME`://`TAIGA_SITES_DOMAIN`. Where this Taiga instance should be served. It should be the same as `TAIGA_SITES_SCHEME`://`TAIGA_SITES_DOMAIN`.
##### `TAIGA_WEBSOCKETS_URL` ##### `TAIGA_WEBSOCKETS_URL`
To connect to the events. This should have the same value as `TAIGA_SITES_DOMAIN`, ie: ws://taiga.mycompany.com To connect to the events. This should have the same value as `TAIGA_SITES_DOMAIN`, ie: ws://taiga.mycompany.com
@ -185,4 +192,4 @@ Default access for the application is **http://localhost:9000**.
```sh ```sh
$ docker-compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage [COMMAND] $ docker-compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage [COMMAND]
``` ```

View File

@ -20,6 +20,8 @@ x-environment:
# EMAIL_PORT: 587 # EMAIL_PORT: 587
# EMAIL_HOST_USER: "user" # EMAIL_HOST_USER: "user"
# EMAIL_HOST_PASSWORD: "password" # EMAIL_HOST_PASSWORD: "password"
# Telemetry settings
ENABLE_TELEMETRY: "True"
# Rabbitmq settings # Rabbitmq settings
# should be the same as in taiga-async-rabbitmq and taiga-events-rabbitmq # should be the same as in taiga-async-rabbitmq and taiga-events-rabbitmq
RABBITMQ_USER: taiga RABBITMQ_USER: taiga
@ -54,6 +56,8 @@ services:
- taiga-db-data:/var/lib/postgresql/data - taiga-db-data:/var/lib/postgresql/data
networks: networks:
- taiga - taiga
ports:
- "5432:5432"
taiga-back: taiga-back:
image: taigaio/taiga-back:alpha image: taigaio/taiga-back:alpha