Operating System CentOS

How to Install Taiga Project Management on AlmaLinux 9 or Rocky Linux 9

Run Taiga on AlmaLinux 9 or Rocky Linux 9 using the official Docker deployment, with Nginx and Let's Encrypt in front, plus backups and updates.

This guide sets up Taiga, the open-source agile project management tool, on AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9. At the end you will have Taiga running in Docker containers, published at https://taiga.example.com through an Nginx reverse proxy with a Let's Encrypt certificate, and an administrator account to log in with.

CentOS 7 reached end of life in June 2024, so new installations belong on a RHEL 9 compatible system. The way Taiga is installed has changed too: the Taiga documentation recommends the Docker deployment from the taiga-docker repository. A from-source installation is still documented, but only for Ubuntu 20.04 with Python older than 3.12 and PostgreSQL older than 14, which does not match what a RHEL 9 system provides. Docker is therefore the route used here.

Requirements

  • A server running AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9, and a user with sudo rights (deploy in the examples).
  • Docker 19.03.0 or newer with the Compose plugin. The stack starts PostgreSQL, two RabbitMQ instances and several Taiga services, so plan memory for a handful of containers rather than a single process.
  • A DNS record such as taiga.example.com pointing to the server (203.0.113.10 in the examples).
  • An SMTP account if Taiga should send invitations and notifications.

Step 1: Install Docker Engine

Add Docker's repository and install the engine and the Compose plugin. Docker documents this repository for CentOS Stream 9; AlmaLinux 9 and Rocky Linux 9 are RHEL-compatible and use the same packages, although Docker does not list them as tested platforms.

sudo dnf -y install dnf-plugins-core git
sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl enable --now docker

Allow your user to talk to the Docker daemon, then log out and back in so the new group applies:

sudo usermod -aG docker deploy

Step 2: Download and configure Taiga

Clone the deployment repository and switch to the stable branch, which is the one meant for production:

cd ~
git clone https://github.com/taigaio/taiga-docker
cd taiga-docker
git checkout stable

Generate random values for the secrets you are about to set. Run the command once per secret:

openssl rand -hex 32

Open .env in an editor and change at least the following settings. The defaults in the file are public, so do not keep any of the default passwords.

TAIGA_SCHEME=https
TAIGA_DOMAIN=taiga.example.com
SUBPATH=""
WEBSOCKETS_SCHEME=wss

SECRET_KEY="paste-a-generated-value"

POSTGRES_USER=taiga
POSTGRES_PASSWORD=paste-a-generated-value

RABBITMQ_USER=taiga
RABBITMQ_PASS=paste-a-generated-value
RABBITMQ_VHOST=taiga
RABBITMQ_ERLANG_COOKIE=paste-a-generated-value

For outgoing mail, set EMAIL_BACKEND=smtp and fill in EMAIL_HOST, EMAIL_PORT, EMAIL_HOST_USER, EMAIL_HOST_PASSWORD, EMAIL_DEFAULT_FROM and either EMAIL_USE_TLS or EMAIL_USE_SSL. With the default EMAIL_BACKEND=console, messages are only printed to the container log.

Taiga collects anonymous usage telemetry by default. Set ENABLE_TELEMETRY=False in the same file to opt out.

Keep the gateway port private

The taiga-gateway service in docker-compose.yml publishes port 9000 on every network interface, and ports published by Docker are not filtered by your firewalld zone rules. Because Nginx on the host will be the only public entry point, bind the port to the loopback address. In docker-compose.yml, find the taiga-gateway service and change its port mapping from "9000:80" to:

    ports:
      - "127.0.0.1:9000:80"

Step 3: Start Taiga and create the administrator

The repository ships two helper scripts. The first one runs docker compose up -d for you:

./launch-taiga.sh

The first start downloads the images and runs the database migrations, which takes a few minutes. Check that the containers are up:

docker compose ps

Then create the first administrator. The script passes its arguments to Taiga's manage.py inside a temporary container and asks for a user name, e-mail address and password:

./taiga-manage.sh createsuperuser

Step 4: Publish Taiga through Nginx with HTTPS

Install Nginx and allow it to open connections to the local Taiga port, which SELinux blocks by default:

sudo dnf install nginx
sudo setsebool -P httpd_can_network_connect 1
sudo systemctl enable --now nginx

Create /etc/nginx/conf.d/taiga.conf with the proxy configuration from the Taiga documentation. The second location carries the WebSocket connection that pushes live updates to the browser.

server {
    listen 80;
    server_name taiga.example.com;

    client_max_body_size 50M;

    location / {
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect off;
        proxy_pass http://localhost:9000/;
    }

    location /events {
        proxy_pass http://localhost:9000/events;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_connect_timeout 7d;
        proxy_send_timeout 7d;
        proxy_read_timeout 7d;
    }
}

Test the configuration, reload Nginx and open the web ports:

sudo nginx -t
sudo systemctl reload nginx
sudo firewall-cmd --permanent --add-service=http --add-service=https
sudo firewall-cmd --reload

Request a certificate with Certbot from the EPEL repository. Certbot adds the TLS settings and the redirect to the server block you just created:

sudo dnf install epel-release
sudo dnf install certbot python3-certbot-nginx
sudo certbot --nginx -d taiga.example.com

Step 5: Verify the installation

Open https://taiga.example.com and sign in with the account from step 3. Create a test project and keep it open in two browser windows: a change made in one window should appear in the other without a reload, which confirms that the /events WebSocket proxy works.

If the page does not load, look at the logs of the gateway and back-end containers:

cd ~/taiga-docker
docker compose logs --tail=50 taiga-gateway taiga-back

Two problems are common. A login that fails or links that point to localhost:9000 mean TAIGA_SCHEME, TAIGA_DOMAIN or WEBSOCKETS_SCHEME in .env do not match the public address; fix them and run ./launch-taiga.sh again to recreate the containers. A back end that cannot connect to the database after you edited POSTGRES_PASSWORD means the database volume was already initialised with the earlier password; the variable only applies when the volume is first created.

Backups and updates

Taiga keeps its data in named Docker volumes: the PostgreSQL database in taiga-db-data and uploaded attachments in taiga-media-data. Dump the database regularly and copy the dump off the server:

cd ~/taiga-docker
docker compose exec -T taiga-db pg_dump -U taiga taiga | gzip > ~/taiga-$(date +%F).sql.gz

The compose file references the Taiga images by the latest tag. To update, back up first, then fetch the current deployment files and images and recreate the containers:

cd ~/taiga-docker
git pull
docker compose pull
./launch-taiga.sh

git pull stops if it would overwrite your edited .env or docker-compose.yml; keep a copy of both files so you can re-apply your settings after an upstream change.

Frequently asked questions

Can I install Taiga on AlmaLinux or Rocky Linux without Docker?

The only non-Docker procedure in the Taiga documentation targets Ubuntu 20.04 and needs Python below 3.12 and PostgreSQL below 14. You would have to adapt every step yourself and maintain five separate services, so the container deployment is the practical choice on a RHEL 9 compatible system.

Can Taiga live under a path such as example.com/taiga?

Yes. Set TAIGA_DOMAIN=example.com and SUBPATH="/taiga" in .env, and proxy /taiga/ and /taiga/events instead of / and /events in Nginx. The Taiga documentation also advises changing the secret key when you move an existing instance between a subdomain and a subpath.

Do I have to use Nginx on the host?

No. Any reverse proxy that terminates TLS and forwards both normal requests and WebSocket upgrades to port 9000 works. What you should not do is expose port 9000 directly to the internet, because the gateway container only speaks plain HTTP.

How do I use Docker on Ubuntu or Debian instead?

Only step 1 and the Nginx packaging differ. Install Docker Engine from Docker's apt repository as described in the Docker installation documentation; the Taiga steps are identical. The Taiga production setup guide lists the remaining optional settings.

Share story:

Continue reading other guides on How VPS.