Skip to content
This repository has been archived by the owner on Oct 10, 2020. It is now read-only.

Latest commit

 

History

History
73 lines (52 loc) · 2.7 KB

README.md

File metadata and controls

73 lines (52 loc) · 2.7 KB
Raw

Taiga Docker Image

This is based on the official Python image (Alpine variant) and combines taiga-back and taiga-front components into a single container, which uses uWSGI to serve them both.

Image discontinued

This image is discontinued and will not receive any further updates at all. If the image becomes inactive on Docker Hub, it will be removed as per Docker Hub image retention policy.

There is now the official fork maintained by Taiga developers themselves and can be used as a drop-in replacement. You can find the sources on their GitHub and the image on their Docker Hub.

Deployment

Consult Taiga: Setup production environment to learn about external dependencies and basic configuration options. A very basic deployment example can be found in docker-compose.yml and an advanced one in docker-compose.advanced.yml.

Configuring taiga-back

taiga-back can be configured using /etc/opt/taiga-back/settings.py. See root/etc/opt/taiga-back/settings.py in this repository for the default configuration and information about all the settings.

Configuring taiga-front

taiga-front can be configured using /etc/opt/taiga-front/conf.json. See conf.example.json for the default configuration.

Configuring uWSGI

uWSGI can be configured using /usr/local/etc/uwsgi/uwsgi.ini and/or using environmental variables. This file provides only the basic configuration, since settings defined in it cannot be overridden using environmental variables. Also, using environmental variables is the easiest way to extend the default configuration without the need duplicate contents on the configuration file.

See Dockerfile to learn about the variables exported by default and their significance.

Graceful shutdown

With the default configuration, uWSGI is shutdown forcefully on SIGTERM and gracefully on SIGHUP.

Persistence

taiga-back persists data such as attachments in /srv/taiga-back/media. This directory is not a volume by default!

Populate the database with initial data

You can populate the database by using populate-db command. Because this command will overwrite existing data, it is not run by default.

Stability

Breaking changes may occur between different image tags, so make sure to review the changes before upgrading. Images tagged with respective Taiga version are guaranteed to be stable.