We’ve got some news for you!
Although the Taiga team is currently focused on TaigaNext and not developing any new features for Taiga6, we have made some interesting changes for the self-hosted instances in the past few weeks.
Firstly, we’ve migrated the Taiga6 API to Django 3.2 and upgraded many dependencies to their newer and more secure versions. In this process, we have dropped support for Python 3.7 and added support for Python 3.11. On the frontend side, we’ve upgraded to Node v16.
These changes are now available in the official images on DockerHub, so we encourage you to upgrade.
Additionally, we have made important changes to the basic taiga-docker configuration process. Taiga6 is composed of several services that require shared configuration. Up until now, the basic configuration has been a bit cumbersome, and the developer had to add the same variable in different places, making sure the values match. This led to configuration failures and generated many questions from users.
The new system unifies the configuration into one .env file. Since this file is reused in all services, it will be much easier to configure self-hosted instances and will avoid common mistakes with the values. We hope this change will help more people to be autonomous in managing a Taiga instance on their servers.
In order to use this new system, we have created several help documents:
- If you’re not using Taiga yet but want to start, deploy a full Taiga service for a production environment using Docker. The easiest and recommended way to run the tool is the “Taiga 30 min Docker Setup”.
- If you’re already using taiga-docker and want to update to the new system, follow the migration guide.
- If you’re on the old system and still don’t want to change, that’s OK. We’ve left this document as an archive, so you can continue using Taiga as you like.
We hope you like these changes and that they make it easier for you to use Taiga for your projects.
