Cleanup readme

This commit is contained in:
erik 2023-09-05 12:34:08 +02:00
parent 0d7b30fe82
commit 6bb4e59a05
2 changed files with 12 additions and 11 deletions

View file

@ -30,8 +30,6 @@ args: ["-c", "source /opt/venv/bin/activate && python manage.py createsuperuser
Thus the dockerfile default entrypoint is ignored.
Problem: Login using this method is still not available with the proposed credentials.
#### Option 1: Init container, currently under test
Create an init container (celery disabled) with the python manage.py command and the taiga-manage createsuperuser args
@ -91,28 +89,31 @@ https://github.com/kaleidos-ventures/taiga-back/blob/main/docker/config.py). The
## Purpose
Easily generate a config for a small scale Taiga deployment. Complete with initial super user and configurable values for flexibility.
## Status
WIP. We still need to implement the backup solution for full functionality.
## Try out
Click on the image to try out live in your browser:
[![Try it out](doc/tryItOut.png "Try out yourself")](https://domaindrivenarchitecture.org/pages/dda-provision/c4k-taiga/)
Your input will stay in your browser. No server interaction is required.
## Usage
You need:
...
* A working DNS route to the FQDN of your taiga installation
* A kubernetes cluster provisioned by [provs]
* The .yaml file generated by c4k-taiga
* and a kubernetes cluster provisioned by [provs]
...
Let c4k-taiga generate your .yaml file.
Apply this file on your cluster with `kubectl apply -f yourApp.yaml`.
Done.
### resource requests and limits
You may want to adjust the resource requests and limits of the build and init containers to your specific scenario.
## Development & mirrors
Development happens at: https://repo.prod.meissa.de/meissa/c4k-taiga

Binary file not shown.

Before

Width:  |  Height:  |  Size: 149 KiB

After

Width:  |  Height:  |  Size: 53 KiB