[Skip-CI] Update Readme
This commit is contained in:
parent
f788634d6b
commit
45965c5aff
1 changed files with 11 additions and 5 deletions
16
README.md
16
README.md
|
@ -41,12 +41,10 @@ sollten für den Container gesetzt sein.
|
|||
|
||||
Dann noch ein run befehl mit: python manage.py createsuperuser im init container unterbringen.
|
||||
|
||||
### Für das deployment
|
||||
### deployment
|
||||
|
||||
taiga reads many values in config.py from env vars:
|
||||
https://github.com/kaleidos-ventures/taiga-back/blob/main/docker/config.py
|
||||
|
||||
Good for postgres
|
||||
Taiga reads many values in config.py from env vars as can be seen in the taiga-back [config.py](
|
||||
https://github.com/kaleidos-ventures/taiga-back/blob/main/docker/config.py).
|
||||
|
||||
Mounting a configmap with a config.py as described here: https://docs.taiga.io/setup-production.html could be interesting. A mix of both env-vars and config.py in one container is not possible.
|
||||
|
||||
|
@ -82,6 +80,14 @@ https://github.com/kaleidos-ventures/taiga-back/blob/main/settings/config.py.pro
|
|||
* email
|
||||
* rabbit-mq
|
||||
|
||||
### Networking
|
||||
|
||||
We need to know what the "hostname" KW does in docker compose.
|
||||
Then need to find a translation for this functionality to kubernetes.
|
||||
|
||||
How do we direct traffic towards the frontend pod?
|
||||
Do we need to touch the frontend config regarding the address of the API?
|
||||
|
||||
## Purpose
|
||||
|
||||
## Status
|
||||
|
|
Loading…
Reference in a new issue