### Start all Taiga services with docker compose up Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Launches all services in detached mode after installation. Use this to bring the stack up. ```bash $ docker compose up -d ``` -------------------------------- ### Quick start commands: launch-taiga.sh and taiga-manage.sh Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/README.md Start the full Taiga stack in detached mode and create the initial Django superuser. The application is then served at http://localhost:9000. ```sh ./launch-taiga.sh # start the full stack in detached mode ./taiga-manage.sh createsuperuser # create the initial Django superuser ``` -------------------------------- ### Launch Taiga with ./launch-taiga.sh Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Starts the Taiga application using Docker Compose. After running, wait for the application to start before creating the superuser. ```sh $ ./launch-taiga.sh ``` -------------------------------- ### Rename taiga-back config.py.prod.example to config.py Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Download the example configuration file from taiga-back and rename it to config.py for editing. ```bash mv settings/config.py.prod.example settings/config.py ``` -------------------------------- ### Rename taiga-front conf.example.json to conf.json Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Download the example configuration file from taiga-front and rename it to conf.json for editing. ```bash mv dist/conf.example.json dist/conf.json ``` -------------------------------- ### URL settings for subdomain deployment Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Example configuration for serving Taiga on a subdomain (e.g., taiga.mycompany.com) with HTTPS and WSS. ```bash TAIGA_SCHEME=https TAIGA_DOMAIN=taiga.mycompany.com SUBPATH="" WEBSOCKETS_SCHEME=wss ``` -------------------------------- ### Create superuser with ./taiga-manage.sh createsuperuser Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Creates the initial superuser for Taiga. Run after the application has started. ```sh $ ./taiga-manage.sh createsuperuser ``` -------------------------------- ### URL settings for subpath deployment Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Example configuration for serving Taiga on a subpath (e.g., /taiga) instead of a subdomain. ```bash TAIGA_SCHEME=https TAIGA_DOMAIN=mycompany.com SUBPATH="/taiga" WEBSOCKETS_SCHEME=wss ``` -------------------------------- ### Configure conf.json for subdomain Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Example JSON configuration for serving Taiga in a subdomain, setting api, eventsUrl, and baseHref. ```json { "api": "https://taiga.mycompany.com/api/v1/", "eventsUrl": "wss://taiga.mycompany.com/events", "baseHref": "/", } ``` -------------------------------- ### Configure Taiga in subdomain (config.py) Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Example configuration for serving Taiga in a subdomain, setting scheme, domain, and no script name. ```python TAIGA_SITES_SCHEME = "https" TAIGA_SITES_DOMAIN = "taiga.mycompany.com" FORCE_SCRIPT_NAME = "" ``` -------------------------------- ### Configure Taiga in subpath (config.py) Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Example configuration for serving Taiga in a subpath, setting scheme, domain, and script name. ```python TAIGA_SITES_SCHEME = "https" TAIGA_SITES_DOMAIN = "taiga.mycompany.com" FORCE_SCRIPT_NAME = "/taiga" ``` -------------------------------- ### Configure conf.json for subpath Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Example JSON configuration for serving Taiga in a subpath, setting api, eventsUrl, and baseHref. ```json { "api": "https://mycompany.com/taiga/api/v1/", "eventsUrl": "wss://mycompany.com/taiga/events", "baseHref": "/taiga/", } ``` -------------------------------- ### Create superuser with docker compose run Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Starts the services in detached mode, then runs the createsuperuser management command in a one-off container to create an admin user. ```bash $ docker compose up -d $ docker compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage createsuperuser ``` -------------------------------- ### Attachments Compose interpolation Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md YAML snippet showing how ATTACHMENTS_MAX_AGE is interpolated for the taiga-protected service. Controls how long protected-attachment tokens remain valid (the README example uses 360 seconds). ```yaml # taiga-protected MAX_AGE: "${ATTACHMENTS_MAX_AGE}" ``` -------------------------------- ### Full docker-compose-inits.yml overlay source Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/api-reference/compose-inits.md Complete YAML for the overlay module. Re-declares x-environment and x-volumes anchors and the taiga-manage service. Requires the main file's network and volumes. ```yaml version: "3.5" x-environment: &default-back-environment # These environment variables will be used by the taiga-manage service. # Database settings POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" POSTGRES_HOST: "taiga-db" # Taiga settings TAIGA_SECRET_KEY: "${SECRET_KEY}" TAIGA_SITES_SCHEME: "${TAIGA_SCHEME}" TAIGA_SITES_DOMAIN: "${TAIGA_DOMAIN}" TAIGA_SUBPATH: "${SUBPATH}" # Email settings EMAIL_BACKEND: "django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend" DEFAULT_FROM_EMAIL: "${EMAIL_DEFAULT_FROM}" EMAIL_USE_TLS: "${EMAIL_USE_TLS}" EMAIL_USE_SSL: "${EMAIL_USE_SSL}" EMAIL_HOST: "${EMAIL_HOST}" EMAIL_PORT: "${EMAIL_PORT}" EMAIL_HOST_USER: "${EMAIL_HOST_USER}" EMAIL_HOST_PASSWORD: "${EMAIL_HOST_PASSWORD}" # Rabbitmq settings RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" # (async discouraged: only used by taiga-events and taiga-protected) # CELERY_ENABLED: "True" # ...customizations go here x-volumes: &default-back-volumes # These volume mounts are used by the taiga-manage service. - taiga-static-data:/taiga-back/static - taiga-media-data:/taiga-back/media # - ./config.py:/taiga-back/settings/config.py services: taiga-manage: image: taigaio/taiga-back:latest environment: *default-back-environment volumes: *default-back-volumes networks: - taiga depends_on: - taiga-db networks: taiga: ``` -------------------------------- ### Run taiga-manage with docker-compose-inits.yml overlay Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/api-reference/compose-inits.md Command to run the taiga-manage service using the overlay file. Must be used with the main docker-compose.yml file. ```sh docker compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage $@ ``` -------------------------------- ### Enable Slack integration (backend and frontend) Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Enable Slack integration by setting ENABLE_SLACK to "True" in the backend and "true" in the frontend. ```yml ENABLE_SLACK: "True" ``` ```yml ENABLE_SLACK: "true" ``` -------------------------------- ### Enable public registration (backend and frontend) Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Enable public registration by setting PUBLIC_REGISTER_ENABLED to "True" in the backend and "true" in the frontend. Note the case difference: backend uses 'True', frontend uses 'true'. ```yml PUBLIC_REGISTER_ENABLED: "True" ``` ```yml PUBLIC_REGISTER_ENABLED: "true" ``` -------------------------------- ### Enable GitLab OAuth login (backend and frontend) Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Enable GitLab OAuth login by setting ENABLE_GITLAB_AUTH to "True" in the backend and "true" in the frontend. GITLAB_API_CLIENT_ID and GITLAB_CLIENT_ID must have the same value, and GITLAB_URL must match. Public registration must be enabled for GitLab login to work. ```yml ENABLE_GITLAB_AUTH: "True" GITLAB_API_CLIENT_ID: "gitlab-client-id" GITLAB_API_CLIENT_SECRET: "gitlab-client-secret" GITLAB_URL: "gitlab-url" PUBLIC_REGISTER_ENABLED: "True" ``` ```yml ENABLE_GITLAB_AUTH: "true" GITLAB_CLIENT_ID: "gitlab-client-id" GITLAB_URL: "gitlab-url" PUBLIC_REGISTER_ENABLED: "true" ``` -------------------------------- ### Compose interpolation for Taiga URL environment variables Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md Shows how docker-compose.yml and docker-compose-inits.yml interpolate TAIGA_SCHEME, TAIGA_DOMAIN, SUBPATH, and WEBSOCKETS_SCHEME from .env into TAIGA_SITES_SCHEME, TAIGA_SITES_DOMAIN, TAIGA_SUBPATH, TAIGA_URL, and TAIGA_WEBSOCKETS_URL. ```yaml TAIGA_SITES_SCHEME: "${TAIGA_SCHEME}" TAIGA_SITES_DOMAIN: "${TAIGA_DOMAIN}" TAIGA_SUBPATH: "${SUBPATH}" TAIGA_URL: "${TAIGA_SCHEME}://${TAIGA_DOMAIN}" TAIGA_WEBSOCKETS_URL: "${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}" ``` -------------------------------- ### Run manage.py commands with ./taiga-manage.sh Source: https://github.com/taigaio/taiga-docker/blob/main/README.md The taiga-manage.sh script allows running manage.py commands on the backend instance. Replace [COMMAND] with the desired command. ```sh $ ./taiga-manage.sh [COMMAND] ``` -------------------------------- ### Enable GitHub OAuth login (backend and frontend) Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Enable GitHub OAuth login by setting ENABLE_GITHUB_AUTH to "True" in the backend and "true" in the frontend. GITHUB_API_CLIENT_ID and GITHUB_CLIENT_ID must have the same value. Public registration must be enabled for GitHub login to work. ```yml ENABLE_GITHUB_AUTH: "True" GITHUB_API_CLIENT_ID: "github-client-id" GITHUB_API_CLIENT_SECRET: "github-client-secret" PUBLIC_REGISTER_ENABLED: "True" ``` ```yml ENABLE_GITHUB_AUTH: "true" GITHUB_CLIENT_ID: "github-client-id" PUBLIC_REGISTER_ENABLED: "true" ``` -------------------------------- ### Email settings: EMAIL_BACKEND and SMTP configuration Source: https://github.com/taigaio/taiga-docker/blob/main/README.md By default, emails are printed to the console. Change EMAIL_BACKEND to 'smtp' and configure the SMTP variables. EMAIL_USE_TLS and EMAIL_USE_SSL are mutually exclusive. ```bash EMAIL_BACKEND=console # use an SMTP server or display the emails in the console (either "smtp" or "console") EMAIL_HOST=smtp.host.example.com # SMTP server address EMAIL_PORT=587 # default SMTP port EMAIL_HOST_USER=user # user to connect the SMTP server EMAIL_HOST_PASSWORD=password # SMTP user's password EMAIL_DEFAULT_FROM=changeme@example.com # email address for the automated emails # EMAIL_USE_TLS/EMAIL_USE_SSL are mutually exclusive (only set one of those to True) EMAIL_USE_TLS=True # use TLS (secure) connection with the SMTP server EMAIL_USE_SSL=False # use implicit TLS (secure) connection with the SMTP server ``` -------------------------------- ### Database settings: POSTGRES_USER and POSTGRES_PASSWORD Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Environment variables used to create and connect to the PostgreSQL database. Change the default values for security. ```bash POSTGRES_USER=taiga # user to connect to PostgreSQL POSTGRES_PASSWORD=taiga # database user's password ``` -------------------------------- ### Compose interpolation for database environment variables Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md Shows how POSTGRES_USER and POSTGRES_PASSWORD from .env are interpolated into taiga-db, the x-environment anchor for taiga-back/taiga-async, and the x-environment anchor for taiga-manage. The database name is fixed as 'taiga' and the host is fixed as 'taiga-db'. ```yaml # docker-compose.yml — taiga-db POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" # docker-compose.yml — x-environment anchor (consumed by taiga-back, taiga-async) POSTGRES_DB: "taiga" # fixed literal POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" POSTGRES_HOST: "taiga-db" # fixed literal (compose service name) # docker-compose-inits.yml — x-environment anchor (consumed by taiga-manage) POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" POSTGRES_HOST: "taiga-db" # fixed literal ``` -------------------------------- ### Public registration environment variables Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md Required for enabling public registration. Must be added to the backend anchor (&default-back-environment) with value "True" and to the taiga-front service with value "true" (note the case difference). ```yaml # backend (&default-back-environment) PUBLIC_REGISTER_ENABLED: "True" # taiga-front PUBLIC_REGISTER_ENABLED: "true" ``` -------------------------------- ### Nginx location /media/exports/ alias for public exports Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Serves project-export bundles from the taiga-media-data volume path /taiga/media/exports/. Unprotected counterpart of /_protected/. Adds Content-Disposition: attachment to trigger download. No authentication required. ```nginx location /media/exports/ { alias /taiga/media/exports/; add_header Content-disposition "attachment"; } ``` -------------------------------- ### Jira Importer Backend Environment Variables Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Add these variables to the `&default-back-environment` section to enable the Jira importer. Use 'True' (capital T) for the backend. Replace the placeholder values with your Jira OAuth credentials. ```yaml ENABLE_JIRA_IMPORTER: "True" JIRA_IMPORTER_CONSUMER_KEY: "consumer-key-from-jira" JIRA_IMPORTER_CERT: "cert-from-jira" JIRA_IMPORTER_PUB_CERT: "pub-cert-from-jira" ``` -------------------------------- ### URL settings: TAIGA_SCHEME, TAIGA_DOMAIN, SUBPATH, WEBSOCKETS_SCHEME Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Variables that set where Taiga is served and the security protocols. The default configuration assumes a subdomain deployment. ```bash TAIGA_SCHEME=http # serve Taiga using "http" or "https" (secured) connection TAIGA_DOMAIN=localhost:9000 # Taiga's base URL SUBPATH="" # it'll be appended to the TAIGA_DOMAIN (use either "" or a "/subpath") WEBSOCKETS_SCHEME=ws # events connection protocol (use either "ws" or "wss") ``` -------------------------------- ### Nginx location / for frontend Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Proxies requests to the frontend service `taiga-front`. Sets Host, X-Real-IP, and X-Scheme headers, passes through the Server header, and disables redirect rewriting. Public entrypoint with no authentication. ```nginx location / { proxy_pass http://taiga-front/; proxy_pass_header Server; proxy_set_header Host $http_host; proxy_redirect off; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; } ``` -------------------------------- ### GitHub Importer Backend Environment Variables Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Add these variables to the `&default-back-environment` section of your docker-compose file to enable the GitHub importer. Use 'True' (capital T) for the backend. Replace the placeholder values with your actual GitHub OAuth App credentials. ```yaml ENABLE_GITHUB_IMPORTER: "True" GITHUB_IMPORTER_CLIENT_ID: "client-id-from-github" GITHUB_IMPORTER_CLIENT_SECRET: "client-secret-from-github" ``` -------------------------------- ### Trello Importer Backend Environment Variables Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Add these variables to the `&default-back-environment` section to enable the Trello importer. Use 'True' (capital T) for the backend. Replace the placeholder values with your Trello API key and secret key. ```yaml ENABLE_TRELLO_IMPORTER: "True" TRELLO_IMPORTER_API_KEY: "api-key-from-trello" TRELLO_IMPORTER_SECRET_KEY: "secret-key-from-trello" ``` -------------------------------- ### docker-compose.yml full source Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/api-reference/compose-main.md The complete docker-compose.yml file for the Taiga platform. It defines services for the database, backend, async worker, RabbitMQ instances, frontend, events, protected, and gateway. It uses YAML anchors for shared environment variables and volumes, and includes healthchecks and dependency conditions. ```yaml version: "3.5" x-environment: &default-back-environment # These environment variables will be used by taiga-back and taiga-async. # Database settings POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" POSTGRES_HOST: "taiga-db" # Taiga settings TAIGA_SECRET_KEY: "${SECRET_KEY}" TAIGA_SITES_SCHEME: "${TAIGA_SCHEME}" TAIGA_SITES_DOMAIN: "${TAIGA_DOMAIN}" TAIGA_SUBPATH: "${SUBPATH}" # Email settings. EMAIL_BACKEND: "django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend" DEFAULT_FROM_EMAIL: "${EMAIL_DEFAULT_FROM}" EMAIL_USE_TLS: "${EMAIL_USE_TLS}" EMAIL_USE_SSL: "${EMAIL_USE_SSL}" EMAIL_HOST: "${EMAIL_HOST}" EMAIL_PORT: "${EMAIL_PORT}" EMAIL_HOST_USER: "${EMAIL_HOST_USER}" EMAIL_HOST_PASSWORD: "${EMAIL_HOST_PASSWORD}" # Rabbitmq settings. RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" RABBITMQ_VHOST: "${RABBITMQ_VHOST}" # ... # Telemetry settings ENABLE_TELEMETRY: "${ENABLE_TELEMETRY}" # ...your customizations go here x-volumes: &default-back-volumes # These volume mounts will be used by taiga-back and taiga-async. - taiga-static-data:/taiga-back/static - taiga-media-data:/taiga-back/media # - ./config.py:/taiga-back/settings/config.py services: taiga-db: image: postgres:12.3 environment: POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" healthcheck: test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER}"] interval: 2s timeout: 15s retries: 5 start_period: 3s volumes: - taiga-db-data:/var/lib/postgresql/data networks: - taiga taiga-back: image: taigaio/taiga-back:latest environment: *default-back-environment volumes: *default-back-volumes networks: - taiga depends_on: taiga-db: condition: service_healthy taiga-events-rabbitmq: condition: service_started taiga-async-rabbitmq: condition: service_started taiga-async: image: taigaio/taiga-back:latest entrypoint: ["/taiga-back/docker/async_entrypoint.sh"] environment: *default-back-environment volumes: *default-back-volumes networks: - taiga depends_on: taiga-db: condition: service_started taiga-events-rabbitmq: condition: service_started taiga-async-rabbitmq: condition: service_started taiga-async-rabbitmq: image: rabbitmq:3.8-management-alpine environment: RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}" RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}" RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}" RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}" hostname: "taiga-async-rabbitmq" volumes: - taiga-async-rabbitmq-data:/var/lib/rabbitmq networks: - taiga taiga-front: image: taigaio/taiga-front:latest environment: TAIGA_URL: "${TAIGA_SCHEME}://${TAIGA_DOMAIN}" TAIGA_WEBSOCKETS_URL: "${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}" TAIGA_SUBPATH: "${SUBPATH}" # ...your customizations go here networks: - taiga # volumes: # - ./conf.json:/usr/share/nginx/html/conf.json taiga-events: image: taigaio/taiga-events:latest environment: RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" TAIGA_SECRET_KEY: "${SECRET_KEY}" networks: - taiga depends_on: taiga-events-rabbitmq: condition: service_started taiga-events-rabbitmq: image: rabbitmq:3.8-management-alpine environment: RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}" RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}" RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}" RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}" hostname: "taiga-events-rabbitmq" volumes: - taiga-events-rabbitmq-data:/var/lib/rabbitmq networks: - taiga taiga-protected: image: taigaio/taiga-protected:latest environment: MAX_AGE: "${ATTACHMENTS_MAX_AGE}" SECRET_KEY: "${SECRET_KEY}" networks: - taiga taiga-gateway: image: nginx:1.19-alpine ports: - "9000:80" volumes: - ./taiga-gateway/taiga.conf:/etc/nginx/conf.d/default.conf - taiga-static-data:/taiga/static - taiga-media-data:/taiga/media networks: - taiga depends_on: - taiga-front - taiga-back - taiga-events volumes: taiga-db-data: taiga-static-data: taiga-media-data: taiga-async-rabbitmq-data: taiga-events-rabbitmq-data: networks: taiga: ``` -------------------------------- ### Nginx location /static/ alias for static assets Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Serves compiled static assets directly from the taiga-static-data volume mounted at /taiga/static. Uses alias instead of proxy_pass, so responses are generated by nginx itself. No authentication required. ```nginx location /static/ { alias /taiga/static/; } ``` -------------------------------- ### GitHub Importer Frontend Environment Variable Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Add this variable to the `taiga-front` service environments to enable the GitHub importer on the frontend. Use 'true' (lowercase) for the frontend. ```yaml ENABLE_GITHUB_IMPORTER: "true" ``` -------------------------------- ### Commented-out advanced config.py volume mounts Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md Shows the commented-out volume mounts for mounting a custom config.py file, which is the 'Advanced configuration' path that bypasses all environment variables. ```yaml # docker-compose.yml x-volumes # - ./config.py:/taiga-back/settings/config.py # docker-compose-inits.yml x-volumes # - ./config.py:/taiga-back/settings/config.py ``` -------------------------------- ### Telemetry settings: ENABLE_TELEMETRY Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Enables anonymous telemetry data collection. Set to False to opt out; default is True. ```bash ENABLE_TELEMETRY=True ``` -------------------------------- ### Trello Importer Frontend Environment Variable Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Add this variable to the `taiga-front` service environments to enable the Trello importer on the frontend. Use 'true' (lowercase) for the frontend. ```yaml ENABLE_TRELLO_IMPORTER: "true" ``` -------------------------------- ### Nginx global server directives Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Sets the gateway as the default server on port 80, limits client upload body size to 100M, and sets the character set to UTF-8. ```nginx listen 80 default_server; # gateway is the default server; host port 9000 → 80 client_max_body_size 100M; # max upload body size (Taiga exports/imports) charset utf-8; ``` -------------------------------- ### Nginx location /api/ for Taiga REST API Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Proxies API requests to `taiga-back:8000/api/`, rewriting the URI. Sets the same headers as the frontend block. Authentication is delegated to the backend; invalid tokens receive a 401. ```nginx location /api/ { proxy_pass http://taiga-back:8000/api/; proxy_pass_header Server; proxy_set_header Host $http_host; proxy_redirect off; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; } ``` -------------------------------- ### Jira Importer Frontend Environment Variable Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Add this variable to the `taiga-front` service environments to enable the Jira importer on the frontend. Use 'true' (lowercase) for the frontend. ```yaml ENABLE_JIRA_IMPORTER: "true" ``` -------------------------------- ### Queue manager settings: RabbitMQ variables Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Variables used to leave messages in the RabbitMQ services. Change the default credentials and cookie. ```bash RABBITMQ_USER=taiga # user to connect to RabbitMQ RABBITMQ_PASS=taiga # RabbitMQ user's password RABBITMQ_VHOST=taiga # RabbitMQ container name RABBITMQ_ERLANG_COOKIE=secret-erlang-cookie # unique value shared by any connected instance of RabbitMQ ``` -------------------------------- ### Compose interpolation for SECRET_KEY environment variable Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md Shows how SECRET_KEY from .env is interpolated into TAIGA_SECRET_KEY for taiga-back and taiga-events, and SECRET_KEY for taiga-protected. The README flags this value as unpredictable and requires it to be shared across these services. ```yaml TAIGA_SECRET_KEY: "${SECRET_KEY}" # taiga-back TAIGA_SECRET_KEY: "${SECRET_KEY}" # taiga-events SECRET_KEY: "${SECRET_KEY}" # taiga-protected ``` -------------------------------- ### Nginx location /_protected/ internal for protected media Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Serves protected media from /taiga/media/ but only for internal subrequests. External requests receive 403 Forbidden. Adds Content-Disposition: attachment header. Only legitimate caller is Nginx itself via X-Accel-Redirect or internal subrequests from taiga-back or taiga-protected. ```nginx location /_protected/ { internal; # 403 when requested by an external client alias /taiga/media/; add_header Content-disposition "attachment"; } ``` -------------------------------- ### Nginx proxy configuration for subdomain deployment Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Nginx server block for serving Taiga on a subdomain (e.g., taiga.mycompany.com). Proxies HTTP and WebSocket events to localhost:9000, with long timeouts for the events endpoint. ```nginx server { server_name taiga.mycompany.com; 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/; } # Events 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; } # TLS: Configure your TLS following the best practices inside your company # Logs and other configurations } ``` -------------------------------- ### RabbitMQ Compose interpolation Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md YAML snippet showing RabbitMQ environment variable interpolation for different services: the x-environment anchor (taiga-back, taiga-async, taiga-events), taiga-events, and the rabbitmq services (taiga-events-rabbitmq / taiga-async-rabbitmq). The Erlang cookie must be a single unique value shared by any connected RabbitMQ instance. ```yaml # x-environment anchor (taiga-back, taiga-async, taiga-events) RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" RABBITMQ_VHOST: "${RABBITMQ_VHOST}" # taiga-events RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" # taiga-events-rabbitmq / taiga-async-rabbitmq RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}" RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}" RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}" RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}" ``` -------------------------------- ### Email/SMTP Compose interpolation Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md YAML snippet showing how email-related environment variables are interpolated in docker-compose. EMAIL_BACKEND is constructed as a fully qualified Django backend class name, e.g., EMAIL_BACKEND=console yields django.core.mail.backends.console.EmailBackend. EMAIL_USE_TLS and EMAIL_USE_SSL are mutually exclusive; set only one to True. ```yaml EMAIL_BACKEND: "django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend" DEFAULT_FROM_EMAIL: "${EMAIL_DEFAULT_FROM}" EMAIL_USE_TLS: "${EMAIL_USE_TLS}" EMAIL_USE_SSL: "${EMAIL_USE_SSL}" EMAIL_HOST: "${EMAIL_HOST}" EMAIL_PORT: "${EMAIL_PORT}" EMAIL_HOST_USER: "${EMAIL_HOST_USER}" EMAIL_HOST_PASSWORD: "${EMAIL_HOST_PASSWORD}" ``` -------------------------------- ### Nginx proxy configuration for subpath deployment Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Nginx server block for serving Taiga under a subpath (e.g., /taiga/). Proxies HTTP and WebSocket events to localhost:9000, with long timeouts for the events endpoint. ```nginx server { server_name mycompany.com; location /taiga/ { 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/; } # Events location /taiga/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; } # TLS: Configure your TLS following the best practices inside your company # Logs and other configurations } ``` -------------------------------- ### Nginx location /events for WebSocket realtime events Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Proxies WebSocket connections to the taiga-events service on port 8888. Forces HTTP/1.1 and forwards the client Upgrade header with Connection: upgrade. Sets connect, send, and read timeouts to 7 days. WebSocket connections are authenticated using TAIGA_SECRET_KEY, matching taiga-back's secret. ```nginx location /events { proxy_pass http://taiga-events:8888/events; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_connect_timeout 7d; proxy_send_timeout 7d; proxy_read_timeout 7d; } ``` -------------------------------- ### Nginx location /media/ for signed protected attachments Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Proxies requests to the taiga-protected service on port 8003. Sets standard proxy headers including Host, X-Real-IP, X-Scheme, X-Forwarded-Proto, and X-Forwarded-For. The URL contains a token signed with SECRET_KEY; invalid or expired tokens are rejected, with expiry controlled by MAX_AGE. ```nginx location /media/ { 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_pass http://taiga-protected:8003/; proxy_redirect off; } ``` -------------------------------- ### Telemetry Compose interpolation Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md YAML snippet showing how ENABLE_TELEMETRY is interpolated. Anonymous telemetry data is collected by default; set to False to opt out. ```yaml ENABLE_TELEMETRY: "${ENABLE_TELEMETRY}" ``` -------------------------------- ### Nginx location /admin/ proxy to Django admin Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/endpoints.md Proxies requests to /admin/ to the taiga-back service's admin URL space. Uses session cookies for authentication, unlike the stateless API. Requires SESSION_COOKIE_SECURE and CSRF_COOKIE_SECURE variables when served over plain HTTP. ```nginx location /admin/ { proxy_pass http://taiga-back:8000/admin/; proxy_pass_header Server; proxy_set_header Host $http_host; proxy_redirect off; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Scheme $scheme; } ``` -------------------------------- ### Django Admin session cookies for HTTP deployments Source: https://github.com/taigaio/taiga-docker/blob/main/_autodocs/configuration.md Add these to &default-back-environment when serving over plain HTTP to disable secure cookie flags. ```yaml SESSION_COOKIE_SECURE: "False" CSRF_COOKIE_SECURE: "False" ``` -------------------------------- ### Secret Key settings: SECRET_KEY Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Sets the secret key used for cryptographic signing. Must be changed to an unpredictable value. ```bash SECRET_KEY="taiga-secret-key" # Please, change it to an unpredictable value! ``` -------------------------------- ### Attachments settings: ATTACHMENTS_MAX_AGE Source: https://github.com/taigaio/taiga-docker/blob/main/README.md Configures the token expiration time for attachment URLs, in seconds. ```bash ATTACHMENTS_MAX_AGE=360 # token expiration date (in seconds) ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.