tyler.durden/taiga-docker
1
0
Fork 0
mirror of https://github.com/taigaio/taiga-docker.git synced 2025-07-31 01:44:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

(chore) Improve session settings documentation

Browse Source
This commit is contained in:
Yamila Moreno 2021-02-17 16:16:50 +01:00
parent bd20a0d957
commit 1fcb875833
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -144,8 +144,7 @@ TAIGA_WEBSOCKETS_URL: "ws://localhost:9000"
### Session Settings
You can add `SESSION_COOKIE_SECURE` and `CSRF_COOKIE_SECURE` to x-environment and change its value. By default is "True", so some browsers only accept https connections.
More info about these environment variables [here](https://docs.djangoproject.com/en/3.1/ref/settings/#csrf-cookie-secure).
Taiga doesn't use session cookies in its API as it stateless. However, the Django Admin (`/admin/`) uses session cookie for authentication. By default, Taiga is configured to work behind HTTPS. If you're using HTTP (despite de strong recommendations against it), you'll need to configure the following environment variables so you can access the Admin:
**Service: taiga-back**
```
@ -153,6 +152,8 @@ SESSION_COOKIE_SECURE: "False"
CSRF_COOKIE_SECURE: "False"
```
More info about those variables can be found [here](https://docs.djangoproject.com/en/3.1/ref/settings/#csrf-cookie-secure).
### Email Settings
By default, email is configured with the *console* backend, which means that the emails will be shown in the stdout. If you have an smtp service, uncomment the "Email settings" section in `docker-compose.yml` and configure those environment variables: