Skip to content

Latest commit

 

History

History
68 lines (45 loc) · 2.67 KB

upgrades-docker-migrate.adoc

File metadata and controls

68 lines (45 loc) · 2.67 KB
Raw

Migrate to new docker settings (v 6.6.0+)

Table of Contents

While taiga-docker has been a pretty successful way for many people to have a Taiga self-hosted, the Taiga team receives a bunch of questions about the docker configuration. We have released a new taiga-docker version with the main settings based in an .env file. The main goal behind this change is to make it way easier to have a basic Taiga up and running.

For those of you who already have a self-hosted Taiga running with docker, this tutorial will guide you through the steps of the migration.

Note
Upgrade to Docker Compose V2

Taiga uses the new Docker Compose V2, because from the end of June 2023 Compose V1 won’t be supported anymore.

Please ensure you have installed docker version 19.03.0+. Now you should be able to use docker compose instead of the old docker-compose command.

1. Summary

If you are familiar with docker and docker compose, this is the sensible summary:

  • save the modifications made in the docker-compose.yml and docker-compose-inits.yml files

  • update the repository taiga-docker

  • add the configuration values to the .env file

  • add the customization values to the docker-compose.yml file

  • launch all services again

That’s it!

2. Step by step

If you are not so familiar with docker or git, these are the comprehensive steps.

2.1. Get and save your current configurations

Make sure to save all the modifications to the docker-compose.yml and docker-compose-inits.yml files. Tipically, you’ll be using the file in the repository, so a git diff will show you all the modifications.

If you have any other modification, trace them as well.

2.2. Update the repository

Download the new version with git fetch && git reset --hard origin/main. Make sure you have now an .env file.

2.3. Add the configuration values to the .env file

Open the .env file and fill the values with the ones you stored previously:

  • Taiga URL

  • Taiga secret key

  • Postgres connection

  • Email configuration

  • RabbitMQ configuration

  • Attachments' token expiration

  • Enable telemetry: we use this anonymous telemetry to improve Taiga. You may want to enable this to help us shape future Taiga.

2.4. Add the customization values to the docker-file.yml file

Customizations are still in the docker-compose.yml file, for instance:

  • GitLat Auth

  • GitHub Importer

2.5. Launch Taiga again

Run docker compose up -d (you may have a slightly different way for this command) and check every service is up and running.