No description

Find a file

Clemens 9201aba498 make superuser creation manual		2024-06-03 10:05:22 +02:00
doc	Add native build	2024-02-23 16:47:24 +01:00
infrastructure/backup	[skip-ci] infrastructure/../test folder removed	2023-12-22 16:55:49 +01:00
public	Remove/Rename c4k-website code	2023-08-24 11:19:56 +02:00
src	make superuser creation manual	2024-06-03 10:05:22 +02:00
.gitignore	Add native build	2024-02-23 16:47:24 +01:00
.gitlab-ci.yml	Use correct image for clj build	2024-02-23 16:53:11 +01:00
build.py	Add native build	2024-02-23 16:47:24 +01:00
LICENSE	Init	2023-07-19 13:44:04 +02:00
package.json	bump version to: 1.1.3-SNAPSHOT	2024-01-19 13:21:35 +01:00
project.clj	Add native build	2024-02-23 16:47:24 +01:00
README.md	make superuser creation manual	2024-06-03 10:05:22 +02:00
shadow-cljs.edn	Use inline-resources macro	2024-02-23 16:20:46 +01:00

README.md

convention 4 kubernetes: c4k-taiga

DeltaChat chat over e-mail | team@social.meissa-gmbh.de | taiga & Blog

Purpose

Easily generate a config for a small scale Taiga deployment. Complete with initial super user and configurable values for flexibility.

Status

Ready for production. We are about to migrate to taiga on our own servers.

Try out

Click on the image to try out live in your browser:

Your input will stay in your browser. No server interaction is required.

Usage

To generate your configuration:

Create an auth.yaml and a config.yaml

You can find examples in src/test/resources/taiga-test in this repository. Please check the def auth? and def config? definitions in src/main/cljc/dda/c4k_taiga/taiga.cljc for required and optional values. When you plan to use the dda_backup solution, you also need the keys:

aws-access-key-id: "AWS_KEY_ID"
aws-secret-access-key: "AWS_KEY_SECRET"
restic-password: ""

in your auth.yaml

and

restic-repository: "repo-path"

in your config.yaml.

install jarwrapper

sudo apt install jarwrapper # on debian derivatives

execute the c4k-taiga-standalone.jar

java -jar c4k-taiga-standalone.jar config.yaml auth.yaml

To set up 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-standalone.jar

Apply this file on your cluster with kubectl apply -f application.yaml.
Done.

Setup

python manage.py createsuperuser --noinput

Administration

You can access the administration of the taiga installation via: your.taiga.url/admin/

In order to login, you first have to create a superuser.

Connect to taiga-back pod: kubectl exec -it taiga-back-deployment-... -- bash
source /opt/venv/bin/activate && python manage.py createsuperuser --noinput

Backup

You need some form of cloud storage like AWS buckets and the respective access credentials to make the backups work correctly.

For a working backup you need to save Taiga DB & Taiga Media as described here: https://docs.taiga.io/backup-and-restore.html

For further instruction please refer to BackupAndRestore.md in doc/ in this repository.

Development & mirrors

Development happens at: https://repo.prod.meissa.de/meissa/c4k-taiga

Mirrors are:

https://gitlab.com/domaindrivenarchitecture/c4k-taiga (issues and PR, CI)
https://github.com/DomainDrivenArchitecture/c4k-taiga

For more details about our repository model see: https://repo.prod.meissa.de/meissa/federate-your-repos