You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
bom f8abf9a414 Use correct image for clj build 3 months ago
doc Add native build 3 months ago
infrastructure/backup [skip-ci] infrastructure/../test folder removed 5 months ago
public Remove/Rename c4k-website code 9 months ago
src Use inline-resources macro 3 months ago
.gitignore Add native build 3 months ago
.gitlab-ci.yml Use correct image for clj build 3 months ago
LICENSE Init 10 months ago
README.md [Skip-CI] Update Readme 7 months ago
build.py Add native build 3 months ago
package.json bump version to: 1.1.3-SNAPSHOT 4 months ago
project.clj Add native build 3 months ago
shadow-cljs.edn Use inline-resources macro 3 months ago

README.md

convention 4 kubernetes: c4k-taiga

Clojars Project pipeline status

DeltaChat chat over e-mail | team@social.meissa-gmbh.de 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:

Try it out

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

Usage

To generate your configuration:

  1. 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.

  1. install jarwrapper
sudo apt install jarwrapper # on debian derivatives
  1. 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.

Administration

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

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:

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

License

Copyright © 2022 meissa GmbH Licensed under the Apache License, Version 2.0 (the "License") Pls. find licenses of our subcomponents here