docker-taiga/taiga

docker-compose.yml for simple taiga setup

Taiga docker setup

About

This is example Docker Compose file for running Taiga project management platform for agile developers, designers and project managers with taiga-events and ssl-enabled reverse proxy with all images based on alpine:latest.

Basic usage

1. Clone this repository. git clone --depth=1 -b master https://github.com/docker-taiga/taiga.git
2. Adjust TAIGA_HOST, TAIGA_SECRET, POSTGRES_PASSWORD and RABBIT_PASSWORD in variables.env file.
3. (Optional) If you want to enable SSL, change TAIGA_SCHEME and TAIGA_PORT variables accordingly, create cert folder and put ssl certificate and key inside. Default certificate and key filenames are fullchain.pem and privkey.pem. This can be changed by adding CERT_NAME and CERT_KEY environment variables to the service proxy. Alternatively, if you use certbot to acquire certificates, point volume /taiga-cert of the proxy service to the location of certificates, e.g. /etc/letsencrypt/live/yourdomain.com.
4. docker-compose --env-file variables.env up

The default username and password taiga creates is admin with password 123123.

Upgrading from Taiga v5 to v6

IMPORTANT: Please read and follow the steps outlined in the official document in order to migrate data and port configuration to the new version.

Individual images

• Taiga backend docker pull dockertaiga/back
• Taiga frontend docker pull dockertaiga/front
• RabbitMQ server docker pull dockertaiga/rabbit
• Taiga events docker pull dockertaiga/events
• Nginx reverse proxy docker pull dockertaiga/proxy

Environment variables

• TAIGA_HOST - Taiga hostname to use with this taiga setup.
• TAIGA_SCHEME - Taiga URL scheme (http/https). Default is 'http'.
• TAIGA_PORT - Taiga port to use. Default is 80.
• TAIGA_BACK_HOST - Backend hostname. Default is back service.
• TAIGA_FRONT_HOST - Frontend hostname. Default is front service.
• EVENTS_HOST - Events hostname. Default is events service.
• TAIGA_SECRET - Django secret key.

---

• ENABLE_SSL - Enable SSL termination (yes/no). Default is 'no'.
• CERT_NAME - Name of certificate file. Default is fullchain.pem.
• CERT_KEY - Name of certificate key file. Default is privkey.pem.

---

• POSTGRES_HOST - PostgeSQL hostname. Default is db service.
• POSTGRES_DB - Database name.
• POSTGRES_USER - PostgreSQL username.
• POSTGRES_PASSWORD - PostgreSQL password.

---

• RABBIT_HOST - RabbitMQ hostname. Default is rabbit service.
• RABBIT_USER - RabbitMQ username.
• RABBIT_PASSWORD - RabbitMQ password.
• RABBIT_VHOST - RabbitMQ virtual host name.

Configuration

By default configuration volume is ./conf with config files ./conf/back/config.py for backend, ./conf/front/config.json for frontend and ./conf/proxy/nginx.conf for reverse proxy. Generated config files are placed here on first run and can be modified to specify e.g. SMTP server configuration.

Persistence

Volume ./data contains postgresql data and taiga media files for persistence and backup purposes.

Upgrading

Before upgrading be sure to check taiga-back changelog for any breaking changes and check for any modified configuration files in this repo to see what configs need to be adjusted accordignly.

1. Update the version in variables.env or pull from this repo.
2. docker-compose --env-file variables.env pull
3. docker-compose --env-file variables.env up

taiga's Issues

Specify port

Seems front container not support special ports:

I use https://sample.domain.com:48642 with special port, but discover send request to https://sample.domain.com/api/v1/stats/discover

Base url must be good option for front container.

Move configuration options from docker-compose.yml to env_file (s)

Add versions tags to docker hub images

Hi! Good practice add tags with versions for images.

You images:

Good practice:

Production ready?

Hi, I would like to know whether it is production ready or not.
Thanks.

Add container letsencrypt to docker-compose.yml

Can't view Issues, but can create them( Error: Something happened and our Oompa Loompas are working on it.)

Hi,

I setup my taiga instance and made a few test users. On one of my users, I created a sample scrum, and created a few issues. The issues create fine, but whenever I click on them I get the error: Something happened and our Oompa Loompas are working on it.

What additional error logs would you need to help troubleshoot this issue? Happy to provide additional context just let me know what!

Thanks!

Problem with SSL

I turned on ENABLE_SSL='yes' but it didn't work. The generated linked "conf/nginx.conf" is always the non-SSL one. So I forked and rebuilt your proxy repo like this (even set a fixed "yes")

INITIAL_SETUP_LOCK=/taiga-conf/.initial_setup.lock

ENABLE_SSL='yes'
if [ "$ENABLE_SSL" = 'yes' ]; then
   echo SSL turned on!
   CONFIG_FILE=nginx_ssl.conf
else
   echo No SSL
   CONFIG_FILE=nginx.conf
fi

if [ ! -f $INITIAL_SETUP_LOCK ]; then
    touch $INITIAL_SETUP_LOCK
    sed -e 's/$TAIGA_HOST/'$TAIGA_HOST'/' \
        -e 's/$TAIGA_BACK_HOST/'$TAIGA_BACK_HOST'/' \
        -e 's/$TAIGA_FRONT_HOST/'$TAIGA_FRONT_HOST'/' \
        -e 's/$EVENTS_HOST/'$EVENTS_HOST'/' \
        -e 's/$CERT_NAME/'$CERT_NAME'/' \
        -e 's/$CERT_KEY/'$CERT_KEY'/' \
        -i /tmp/taiga-conf/$CONFIG_FILE
    cp /tmp/taiga-conf/$CONFIG_FILE /taiga-conf/nginx.conf
    ln -sf /taiga-conf/nginx.conf /etc/nginx/conf.d/nginx.conf
    cp /tmp/taiga-conf/proxy_params /taiga-conf/proxy_params
    ln -sf /taiga-conf/proxy_params /etc/nginx/proxy_params
else
    ln -sf /taiga-conf/nginx.conf /etc/nginx/conf.d/nginx.conf
    ln -sf /taiga-conf/proxy_params /etc/nginx/proxy_params
fi

exec nginx -g 'daemon off;'

I also had certificates in "cert" folder.

After docker-compose up --force-recreate -d, it shows many errors (502 Bad Gateway)

Could you please take a look what was wrong with my configuration? Has anyone tried SSL turned on?

could not translate host name "$POSTGRES_HOST" to address: Name does not resolve

Hello,

Not sure whether I should post here or rather under "docker-taiga/back" since the issue seems to be Django related, but it seems posting here makes more sense as a "centralized" issue reports point.

Trying to deploy docker-taiga on my workstation, I configured the variable.env file in the simplest possible way, i.e. just specifying TAIGA_HOST, TAIGA_SECRET, POSTGRES_PASSWORD, RABBIT_PASSWORD and REDIS_PASSWORD values, leaving all other ones to their defaults.

Running docker-compose up starts all the expected containers but, in the outputted logs, the following error is reported:
django.db.utils.OperationalError: could not translate host name "$POSTGRES_HOST" to address: Name does not resolve

Connecting to the taiga-back container, using docker exec -it taiga-back /bin/sh, showed that the environment variable was well set and that the db hostname was well recognized inside the container:

$ docker exec -it taiga-back /bin/sh
srv/taiga/back # echo ${POSTGRES_HOST}
db
srv/taiga/back # ping -c 3 ${POSTGRES_HOST}
PING db (172.24.0.4): 56 data bytes
64 bytes from 172.24.0.4: seq=0 ttl=64 time=0.184 ms
64 bytes from 172.24.0.4: seq=1 ttl=64 time=0.164 ms
64 bytes from 172.24.0.4: seq=2 ttl=64 time=0.162 ms

--- db ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.162/0.170/0.184 ms

Looking at the settings/local.py file one can see that Django's DATABASES settings are indeed set as follow:

DATABASES = {
    "default": {
        "ENGINE": "django.db.backends.postgresql",
        "NAME": "$POSTGRES_DB",
        "HOST": "$POSTGRES_HOST",
        "USER": "$POSTGRES_USER",
        "PASSWORD": "$POSTGRES_PASSWORD"
    }
}

Not having enough experience with Django, I only can suspect that the $NAMES values do not get substituted with their equivalent environment variables values. But I wonder why this seems to be working for other users and not for me (since I didn't find someone reporting this problem in previous issues).

Thank you very much for any hint that could lead me to a working solution.

Recently repulled; nothing loads; no error messages

Hi everyone,

Thanks as ever for providing this. I'm having a bizarre issue, though. After a year of continuous operation, I shut down and repulled all the images last week. It worked for 8 days. Now, however, the page doesn't load at all (not even getting sad messages about Oompa Loompas). I can see the GET request is reaching the frontend, as both the frontend and the proxy print it out.

I have shut down, deleted containers and restarted. I have repulled the images to check for updates. Both no effect.

There are no error messages, which is the really bizzare thing. I'm just not sure where to go from here and any assistance would be greatly appreciated.

SSL/TLS for taiga in dockers with Nginx

I have some some_domain for taiga. I have installed taiga according to this topic. Then i 've changed some variables in docker-compose.yml:
TAIGA_SITES_SCHEME: "https"
TAIGA_SITES_DOMAIN: "some_domain"
TAIGA_URL: "https://some_domain"
TAIGA_WEBSOCKETS_URL: "wss://some_domain"

Here is my nginx config:

server {
    if ($host = some_domain) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


  server_name some_domain;
  listen 80;
  location / {
    return 301 https://$host$request_uri;
  }


}
server {
  listen [::]:444 ssl; # managed by Certbot
  listen 444 ssl; # managed by Certbot
  server_name some_domain;

  access_log /var/log/tasks_services.log;
  error_log /var/log/tasks_services_error.log;
    ssl_certificate /etc/letsencrypt/live/some_domain/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/some_domain/privkey.pem; # managed by Certbot
  include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
  ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

  ssl_trusted_certificate /etc/letsencrypt/live/some_domain/chain.pem; # managed by Certbot
  ssl_stapling on; # managed by Certbot
  ssl_stapling_verify on; # managed by Certbot
  
  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

}

But while accessing https://some_domain in browser i have
Something happened and the Taiga has captured the error to be able to work on it.

What am i doing wrong?

README instructions giving incorrect branch

Was copy & pasting for efficiency and noticed the README tells to clone from "latest", which is invalid. Hopefully everyone knows what to do when this happens, but figured its also easy to do a quick update to the README

Self signed certificate for email

Hi guys!

I'm runing ok the docker container for taiga and penpot, but i have problems with the email side. I put all the data correctly and test with an script. But the email has a self signed certificate, maybe because that the site doesn't send anything, there are a way to enable the ss certificate?

Thanks best regards!

Alternative container

Hi, I also created a container, maybe you would like to connect efforts?

Features:

• Production-ready setup (using gunicorn instead of python's built-in development server)
• Automatic building of each new Taiga release on Travis CI (using for-each-github-release toolkit from RiotKit CI Utils)
• Stable versioning (tagged releases + dated snapshots)
• Automatic documentation in README.md generated from parsed ENV variables and comments placed in Dockerfile

The project is at:
https://github.com/riotkit-org/docker-taiga

Rebuild images up to 4.0.4 version and upload to hub.docker.com

Taiga version in images 3.4.5
Current version: 4.0.4

https://github.com/taigaio/taiga-back/releases

Provide Helm chart

Provide Helm chart to run taiga without hassle on kubernetes.

Apache reverse proxy

Hi,

Can someone point me out how to configure reverse proxy in apache? Seems I am having problems with ws sockets:

app.js:3267 WebSocket connection to 'ws://127.0.0.1:880/events/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

My apache settings:

ProxyPreserveHost On
ProxyPass         / http://127.0.0.1:880/
ProxyPassReverse  / http://127.0.0.1:880/
ProxyPass         /events ws://127.0.0.1:880/events

NOTE: 880 is the port assigned in docker-compose.yml (ports: - 880:80)

Currently running in OS Ubuntu 18.04.

Thanks.

Cannot access /admin when running on other port than 80

Hello again,

I have managed to get most of the project working on port 8080, but some features like /admin do not work. As the Taiga documentation is pretty laconic, I’m not sure if it’s supposed to be there but the behaviour is definitely weird.

Additionally, emails sending does not work either.

Steps to reproduce:

• Clone the repo
• Change TAIGA_HOST to the machine’s public URL and TAIGA_PORT to 8080
• Change docker-compose.yml to redirect the host’s 8080 port to the proxy’s 80

Result:

• Creating projects and tasks works
• Updating user picture and password works
• /admin and /api return Not Found - The requested resource was not found on this server. and not the standard Taiga 404 error
• /media weirdly redirect me to /media on the 80 port of the host
• /events returns Upgrade Required
• /test properly shows the Taiga 404 page
• Sending emails to invite new users does not work (despite the UX saying it did)

Update the image on docker hub

The image on hub.docker.com is no longer up to date. Recently I had a problem, that the installation was a bit out-dated and I wanted to have the most recent version. I now built it on my own but this would be better done centrally in the official images.

Something happened and our Oompa Loompas are working on it

hello y run the docker-compos but not found

Something happened and the Taiga has captured the error to be able to work on it.

After installation, when I visit the website I get above error.

Conflict of version for urllib3 using some extensions

Do you want to request a feature or report a bug?

Seems like a bug (non-critical)

What is the current behavior?

I've a warning in the logs of my backend container:

Trying import local.py settings...
/usr/lib/python3.7/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.2) or chardet (3.0.4) doesn't match a supported version!
  RequestsDependencyWarning)

I also have an error on the docker build:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
requests 2.21.0 requires urllib3<1.25,>=1.21.1, but you have urllib3 1.26.2 which is incompatible.

If the current behavior is a bug, please provide the steps to reproduce.

Just pick the following Dockerfile and try to build it:

FROM dockertaiga/back

RUN pip3 install --upgrade pip && \
    pip3 install django-storages boto3 taiga-contrib-slack

What is the expected behavior?

Is it happening in taiga.io or in your own instance?

My own instance.

N.B: I've also opened an issue here because I'm not sure if it comes from the last version of taiga or the embeded version of this image.

Thanks for your help!

How hard would it be to make this work behind traefik instead of nginx

I have Traefik working already I don't need to reverse engineer nginx if at all possible. Is it possible to do that with this?

Everything default with Something happened and our Oompa Loompas are working on it.

Hi

I just cloned the git repo and only changed the ports (25080:80, no ssl) since I already have stuff running on those ports. And I am getting the message above.

There are no errors the docker logs that I can tell, and it is a long log.

I added taiga.lan to dns so it is resolvable as you see.

ping taiga.lan
PING taiga.lan (192.168.1.100) 56(84) bytes of data.
64 bytes from neoplecxus.com (192.168.1.100): icmp_seq=1 ttl=64 time=2.14 ms

The only thing I see is in the browser console

downloadable font: kern: Too large subtable (font-family: "OpenSans-Semibold" style:normal weight:400 stretch:100 src index:0) source: http://192.168.5.106:25080/v-1580925907841/fonts/OpenSans-Semibold.ttf
downloadable font: Table discarded (font-family: "OpenSans-Semibold" style:normal weight:400 stretch:100 src index:0) source: http://192.168.5.106:25080/v-1580925907841/fonts/OpenSans-Semibold.ttf
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://taiga.lan/api/v1/stats/discover. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://taiga.lan/api/v1/projects?discover_mode=true&is_featured=true. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://taiga.lan/api/v1/projects?discover_mode=true&order_by=-total_activity_last_week. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://taiga.lan/api/v1/projects?discover_mode=true&order_by=-total_fans_last_week. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://taiga.lan/api/v1/stats/discover. (Reason: CORS request did not succeed).

Not working other port than 80

Hi, when I try to set another port than 80 (ex, 880) in docker-compose.yml, then when I open http://ip:880 just gives me an error (which I can't find what is going on).

It does work with default 80 port (didnt tested SSL with an alternative 443 port).

Any ideas?

Thanks.

Taiga Something happened and the Taiga has captured the error to be able to work on it. Take me home

Taiga can be reached on the system it is installed, but if I access taiga from a different computer on the network I always get the same error (see title).

I have the newest version, downloaded from github.
I looked at the following issue #48
but it did not resolve the problem. What can I do? How can I debug the problem?

Issues on creds and rabbit container keeps restarting

I have everything setup with traefik 2 and I encountered some issues.

.env

TAIGA_HOST=taiga.john.site.dev
TAIGA_SCHEME=https
TAIGA_BACK_HOST=back
TAIGA_FRONT_HOST=front
EVENTS_HOST=events
TAIGA_SECRET=secret

POSTGRES_HOST=db
POSTGRES_DB=taiga
POSTGRES_USER=postgres
POSTGRES_PASSWORD=password

RABBIT_HOST=rabbit
RABBIT_USER=taiga
RABBIT_PASSWORD=password
RABBIT_VHOST=taiga

REDIS_HOST=redis
REDIS_DB=0
REDIS_PASSWORD=password

ENABLE_SSL=no

docker-compose.yml

version: '3'

services:
  back:
    image: dockertaiga/back:5.0.12
    container_name: taiga-back
    restart: unless-stopped
    labels:
      - "traefik.enable=false"
    depends_on:
      - db
      - events
    env_file:
      - .env
    volumes:
      - /srv/taiga/data:/taiga-media
      - /srv/taiga/config/back:/taiga-conf
    networks:
      - default

  front:
    image: dockertaiga/front:5.0.12
    container_name: taiga-front
    restart: unless-stopped
    labels:
      - "traefik.enable=true"
      ... some traefik config ...
    env_file:
      - .env
    volumes:
      - /srv/taiga/config/front:/taiga-conf

  db:
    image: postgres:11-alpine
    container_name: taiga-db
    restart: unless-stopped
    env_file:
      - .env
    volumes:
      - /srv/taiga/postgres:/var/lib/postgresql/data
    networks:
      - default

  rabbit:
    image: dockertaiga/rabbit
    container_name: taiga-rabbit
    restart: unless-stopped
    env_file:
      - .env
    networks:
      - default

  redis:
    image: bitnami/redis:5.0
    container_name: taiga-redis
    env_file:
      - .env
    networks:
      - default

  events:
    image: dockertaiga/events
    container_name: taiga-events
    restart: unless-stopped
    depends_on:
      - rabbit
    env_file:
      - .env
    networks:
      - default

networks:
  default:
    external:
      name: traefik_default

1. With events, rabbit commented out:
   I was able to access the front-end in the browser but I cannot login. I am getting incorrect username and password. I used admin and 123123.

2. Enabled events and rabbit.
   Rabbit container keeps restarting with the container logs below:

$ docker logs taiga-rabbit -f
Waiting for rabbitmq to start...
Waiting for pid file '/var/lib/rabbitmq/rabbitmq.pid' to appear
pid is 7
Waiting for erlang distribution on node 'rabbit@taiga' while OS process '7' is running
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
Error:
process_not_running
Initializing rabbitmq vhost and user...
Error: unable to perform an operation on node 'rabbit@taiga'. Please see diagnostics information and suggestions below.

Most common reasons for this are:

 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running

In addition to the diagnostics info below:

 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@taiga
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools

DIAGNOSTICS
===========

attempted to contact: [rabbit@taiga]

rabbit@taiga:
  * unable to connect to epmd (port 4369) on taiga: nxdomain (non-existing domain)


Current node details:
 * node name: 'rabbitmqcli-413-rabbit@taiga'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: 6g/cRN/9hEC94MMLQ4aQlw==

Error: unable to perform an operation on node 'rabbit@taiga'. Please see diagnostics information and suggestions below.

Most common reasons for this are:

 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running

In addition to the diagnostics info below:

 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@taiga
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools

DIAGNOSTICS
===========

attempted to contact: [rabbit@taiga]

rabbit@taiga:
  * unable to connect to epmd (port 4369) on taiga: nxdomain (non-existing domain)


Current node details:
 * node name: 'rabbitmqcli-520-rabbit@taiga'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: 6g/cRN/9hEC94MMLQ4aQlw==

Error: unable to perform an operation on node 'rabbit@taiga'. Please see diagnostics information and suggestions below.

Most common reasons for this are:

 * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
 * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
 * Target node is not running

In addition to the diagnostics info below:

 * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
 * Consult server logs on node rabbit@taiga
 * If target node is configured to use long node names, don't forget to use --longnames with CLI tools

DIAGNOSTICS
===========

attempted to contact: [rabbit@taiga]

rabbit@taiga:
  * unable to connect to epmd (port 4369) on taiga: nxdomain (non-existing domain)


Current node details:
 * node name: 'rabbitmqcli-627-rabbit@taiga'
 * effective user's home directory: /var/lib/rabbitmq
 * Erlang cookie hash: 6g/cRN/9hEC94MMLQ4aQlw==

ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)
ERROR: epmd error for host taiga: nxdomain (non-existing domain)

Pin postgres to a major version tag?

I just restarted my setup based on this docker-compose config and got surprised by my instance not coming up now because postgres got a major version bump. I didn't find any guidance on ideal postgres version other than >= 9.4

Would it make sense to specify a major version tag for postgres in docker-compose?

Try test taiga as localhost -- Something happened and our Oompa Loompas are working on it.

As suggested in #18

variables.env

TAIGA_HOST=localhost
TAIGA_SCHEME=http
TAIGA_BACK_HOST=back
TAIGA_FRONT_HOST=front
EVENTS_HOST=events
TAIGA_SECRET=secret

ENABLE_SSL=no
# CERT_NAME=fullchain.pem
# CERT_KEY=privkey.pem

POSTGRES_HOST=db
POSTGRES_DB=taiga
POSTGRES_USER=postgres
POSTGRES_PASSWORD=password

RABBIT_HOST=rabbit
RABBIT_USER=taiga
RABBIT_PASSWORD=password
RABBIT_VHOST=taiga

STARTUP_TIMEOUT=15s

logs from docker-compose up

docker-compose up                                                                                                                               ±[●●][latest]
WARNING: The Docker Engine you're using is running in swarm mode.

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, use `docker stack deploy`.

Starting taiga-front  ... done
Starting taiga-db     ... done
Starting taiga-rabbit ... done
Starting taiga-events ... done
Starting taiga-back   ... done
Starting taiga-proxy  ... done
Attaching to taiga-rabbit, taiga-front, taiga-db, taiga-events, taiga-back, taiga-proxy
taiga-db  | The files belonging to this database system will be owned by user "postgres".
taiga-db  | This user must also own the server process.
taiga-db  | 
taiga-db  | The database cluster will be initialized with locale "en_US.utf8".
taiga-db  | The default database encoding has accordingly been set to "UTF8".
taiga-db  | The default text search configuration will be set to "english".
taiga-db  | 
taiga-db  | Data page checksums are disabled.
taiga-db  | 
taiga-db  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
taiga-back | Waiting for database to become ready...
taiga-db  | creating subdirectories ... ok
taiga-db  | selecting default max_connections ... 100
taiga-db  | selecting default shared_buffers ... 128MB
taiga-db  | selecting default timezone ... UTC
taiga-db  | selecting dynamic shared memory implementation ... posix
taiga-db  | creating configuration files ... ok
taiga-db  | running bootstrap script ... ok
taiga-db  | performing post-bootstrap initialization ... sh: locale: not found
taiga-db  | 2019-11-20 13:39:59.730 UTC [30] WARNING:  no usable system locales were found
taiga-db  | ok
taiga-db  | syncing data to disk ... ok
taiga-db  | 
taiga-db  | WARNING: enabling "trust" authentication for local connections
taiga-db  | You can change this by editing pg_hba.conf or using the option -A, or
taiga-db  | --auth-local and --auth-host, the next time you run initdb.
taiga-db  | 
taiga-db  | Success. You can now start the database server using:
taiga-db  | 
taiga-db  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
taiga-db  | 
taiga-db  | waiting for server to start....2019-11-20 13:40:00.576 UTC [35] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
taiga-db  | 2019-11-20 13:40:00.600 UTC [36] LOG:  database system was shut down at 2019-11-20 13:40:00 UTC
taiga-db  | 2019-11-20 13:40:00.608 UTC [35] LOG:  database system is ready to accept connections
taiga-db  |  done
taiga-db  | server started
taiga-db  | CREATE DATABASE
taiga-db  | 
taiga-db  | 
taiga-db  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
taiga-db  | 
taiga-db  | 2019-11-20 13:40:01.037 UTC [35] LOG:  received fast shutdown request
taiga-db  | waiting for server to shut down....2019-11-20 13:40:01.039 UTC [35] LOG:  aborting any active transactions
taiga-db  | 2019-11-20 13:40:01.039 UTC [35] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
taiga-db  | 2019-11-20 13:40:01.049 UTC [37] LOG:  shutting down
taiga-db  | 2019-11-20 13:40:01.065 UTC [35] LOG:  database system is shut down
taiga-db  |  done
taiga-db  | server stopped
taiga-db  | 
taiga-db  | PostgreSQL init process complete; ready for start up.
taiga-db  | 
taiga-db  | 2019-11-20 13:40:01.149 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
taiga-db  | 2019-11-20 13:40:01.149 UTC [1] LOG:  listening on IPv6 address "::", port 5432
taiga-db  | 2019-11-20 13:40:01.152 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
taiga-db  | 2019-11-20 13:40:01.175 UTC [46] LOG:  database system was shut down at 2019-11-20 13:40:01 UTC
taiga-db  | 2019-11-20 13:40:01.181 UTC [1] LOG:  database system is ready to accept connections
taiga-rabbit | 2019-11-20 13:40:04.671 [info] <0.33.0> Application lager started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.799 [info] <0.33.0> Application recon started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.799 [info] <0.33.0> Application xmerl started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.816 [info] <0.33.0> Application mnesia started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.817 [info] <0.33.0> Application inets started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.817 [info] <0.33.0> Application os_mon started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.818 [info] <0.33.0> Application crypto started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.818 [info] <0.33.0> Application jsx started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.818 [info] <0.33.0> Application asn1 started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.818 [info] <0.33.0> Application public_key started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.818 [info] <0.33.0> Application ssl started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.819 [info] <0.33.0> Application ranch started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.819 [info] <0.33.0> Application ranch_proxy_protocol started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.819 [info] <0.33.0> Application rabbit_common started on node rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.821 [info] <0.210.0> 
taiga-rabbit |  Starting RabbitMQ 3.7.3 on Erlang 20.1.7
taiga-rabbit |  Copyright (C) 2007-2018 Pivotal Software, Inc.
taiga-rabbit |  Licensed under the MPL.  See http://www.rabbitmq.com/
taiga-rabbit | 
taiga-rabbit |   ##  ##
taiga-rabbit |   ##  ##      RabbitMQ 3.7.3. Copyright (C) 2007-2018 Pivotal Software, Inc.
taiga-rabbit |   ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
taiga-rabbit |   ######  ##
taiga-rabbit |   ##########  Logs: <stdout>
taiga-rabbit | 
taiga-rabbit |               Starting broker...
taiga-rabbit | 2019-11-20 13:40:07.822 [info] <0.210.0> 
taiga-rabbit |  node           : rabbit@32bc300e95b0
taiga-rabbit |  home dir       : /var/lib/rabbitmq
taiga-rabbit |  config file(s) : /etc/rabbitmq/rabbitmq.conf
taiga-rabbit |  cookie hash    : BwFQOc0qTe95mWzQKpJSDg==
taiga-rabbit |  log(s)         : <stdout>
taiga-rabbit |  database dir   : /var/lib/rabbitmq/mnesia/rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.862 [info] <0.249.0> Memory high watermark set to 3142 MiB (3294860083 bytes) of 7855 MiB (8237150208 bytes) total
taiga-rabbit | 2019-11-20 13:40:07.869 [info] <0.251.0> Enabling free disk space monitoring
taiga-rabbit | 2019-11-20 13:40:07.869 [info] <0.251.0> Disk free limit set to 50MB
taiga-rabbit | 2019-11-20 13:40:07.873 [info] <0.253.0> Limiting to approx 1048476 file handles (943626 sockets)
taiga-rabbit | 2019-11-20 13:40:07.873 [info] <0.254.0> FHC read buffering:  OFF
taiga-rabbit | 2019-11-20 13:40:07.873 [info] <0.254.0> FHC write buffering: ON
taiga-rabbit | 2019-11-20 13:40:07.877 [info] <0.210.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-rabbit | 2019-11-20 13:40:07.916 [info] <0.210.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-rabbit | 2019-11-20 13:40:07.917 [info] <0.210.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
taiga-rabbit | 2019-11-20 13:40:07.918 [info] <0.210.0> Priority queues enabled, real BQ is rabbit_variable_queue
taiga-rabbit | 2019-11-20 13:40:07.922 [info] <0.278.0> Starting rabbit_node_monitor
taiga-rabbit | 2019-11-20 13:40:07.953 [info] <0.304.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@32bc300e95b0/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
taiga-rabbit | 2019-11-20 13:40:07.956 [info] <0.304.0> Starting message stores for vhost '/'
taiga-rabbit | 2019-11-20 13:40:07.957 [info] <0.308.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
taiga-rabbit | 2019-11-20 13:40:07.960 [info] <0.304.0> Started message store of type transient for vhost '/'
taiga-rabbit | 2019-11-20 13:40:07.960 [info] <0.311.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
taiga-rabbit | 2019-11-20 13:40:07.962 [warning] <0.311.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch
taiga-rabbit | 2019-11-20 13:40:07.963 [info] <0.304.0> Started message store of type persistent for vhost '/'
taiga-rabbit | 2019-11-20 13:40:07.967 [info] <0.337.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@32bc300e95b0/msg_stores/vhosts/DUUPSD51ILPPE6LUATO0IN63B' for vhost 'taiga' exists
taiga-rabbit | 2019-11-20 13:40:07.971 [info] <0.337.0> Starting message stores for vhost 'taiga'
taiga-rabbit | 2019-11-20 13:40:07.972 [info] <0.341.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_transient": using rabbit_msg_store_ets_index to provide index
taiga-rabbit | 2019-11-20 13:40:07.974 [info] <0.337.0> Started message store of type transient for vhost 'taiga'
taiga-rabbit | 2019-11-20 13:40:07.974 [info] <0.344.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
taiga-rabbit | 2019-11-20 13:40:07.975 [warning] <0.344.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_persistent": rebuilding indices from scratch
taiga-rabbit | 2019-11-20 13:40:07.976 [info] <0.337.0> Started message store of type persistent for vhost 'taiga'
taiga-rabbit | 2019-11-20 13:40:07.982 [info] <0.386.0> started TCP Listener on [::]:5672
taiga-rabbit | 2019-11-20 13:40:07.982 [info] <0.210.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.982 [info] <0.210.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@32bc300e95b0
taiga-rabbit | 2019-11-20 13:40:07.983 [info] <0.33.0> Application rabbit started on node rabbit@32bc300e95b0
taiga-rabbit |  completed with 0 plugins.
taiga-rabbit | 2019-11-20 13:40:08.267 [info] <0.5.0> Server startup complete; 0 plugins started.
taiga-back | Running database update...
taiga-back | Trying import local.py settings...
taiga-back | Operations to perform:
taiga-back |   Apply all migrations: admin, attachments, auth, bitbucket, contact, contenttypes, custom_attributes, djmail, easy_thumbnails, epics, external_apps, feedback, github, gitlab, gogs, history, issues, likes, milestones, notifications, projects, references, sessions, settings, tasks, timeline, users, userstorage, userstories, votes, webhooks, wiki
taiga-back | Running migrations:
taiga-back |   Applying contenttypes.0001_initial... OK
taiga-back |   Applying users.0001_initial... OK
taiga-back |   Applying admin.0001_initial... OK
taiga-back |   Applying admin.0002_logentry_remove_auto_add... OK
taiga-back |   Applying users.0002_auto_20140903_0916... OK
taiga-back |   Applying projects.0001_initial... OK
taiga-back |   Applying projects.0002_auto_20140903_0920... OK
taiga-back |   Applying attachments.0001_initial... OK
taiga-back |   Applying attachments.0002_add_size_and_name_fields... OK
taiga-back |   Applying attachments.0003_auto_20150114_0954... OK
taiga-back |   Applying attachments.0004_auto_20150508_1141... OK
taiga-back |   Applying attachments.0005_attachment_sha1... OK
taiga-back |   Applying attachments.0006_auto_20160617_1233... OK
taiga-back |   Applying attachments.0007_attachment_from_comment... OK
taiga-back |   Applying attachments.0008_auto_20170201_1053... OK
taiga-back |   Applying contenttypes.0002_remove_content_type_name... OK
taiga-back |   Applying auth.0001_initial... OK
taiga-back |   Applying auth.0002_alter_permission_name_max_length... OK
taiga-back |   Applying auth.0003_alter_user_email_max_length... OK
taiga-back |   Applying auth.0004_alter_user_username_opts... OK
taiga-back |   Applying auth.0005_alter_user_last_login_null... OK
taiga-back |   Applying auth.0006_require_contenttypes_0002... OK
taiga-back |   Applying auth.0007_alter_validators_add_error_messages... OK
taiga-back |   Applying auth.0008_alter_user_username_max_length... OK
taiga-back |   Applying users.0003_auto_20140903_0925... OK
taiga-back |   Applying users.0004_auto_20140913_1914... OK
taiga-back |   Applying users.0005_alter_user_photo... OK
taiga-back |   Applying users.0006_auto_20141030_1132... OK
taiga-back |   Applying bitbucket.0001_initial... OK
taiga-back |   Applying milestones.0001_initial... OK
taiga-back |   Applying issues.0001_initial... OK
taiga-back |   Applying userstories.0001_initial... OK
taiga-back |   Applying userstories.0002_auto_20140903_1301... OK
taiga-back |   Applying userstories.0003_userstory_order_fields... OK
taiga-back |   Applying userstories.0004_auto_20141001_1817... OK
taiga-back |   Applying userstories.0005_auto_20141009_1656... OK
taiga-back |   Applying userstories.0006_auto_20141014_1524... OK
taiga-back |   Applying userstories.0007_userstory_external_reference... OK
taiga-back |   Applying userstories.0008_auto_20141210_1107... OK
taiga-back |   Applying userstories.0009_remove_userstory_is_archived... OK
taiga-back |   Applying projects.0003_auto_20140913_1710... OK
taiga-back |   Applying projects.0004_auto_20141002_2337... OK
taiga-back |   Applying projects.0005_membership_invitation_extra_text... OK
taiga-back |   Applying notifications.0001_initial... OK
taiga-back |   Applying history.0001_initial... OK
taiga-back |   Applying history.0002_auto_20140916_0936... OK
taiga-back |   Applying history.0003_auto_20140917_1405... OK
taiga-back |   Applying history.0004_historyentry_is_hidden... OK
taiga-back |   Applying notifications.0002_historychangenotification... OK
taiga-back |   Applying notifications.0003_auto_20141029_1143... OK
taiga-back |   Applying notifications.0004_watched... OK
taiga-back |   Applying userstories.0010_remove_userstory_watchers... OK
taiga-back |   Applying userstories.0011_userstory_tribe_gig... OK
taiga-back |   Applying tasks.0001_initial... OK
taiga-back |   Applying tasks.0002_tasks_order_fields... OK
taiga-back |   Applying tasks.0003_task_external_reference... OK
taiga-back |   Applying tasks.0004_auto_20141210_1107... OK
taiga-back |   Applying tasks.0005_auto_20150114_0954... OK
taiga-back |   Applying tasks.0006_auto_20150623_1923... OK
taiga-back |   Applying tasks.0007_auto_20150629_1556... OK
taiga-back |   Applying tasks.0008_remove_task_watchers... OK
taiga-back |   Applying tasks.0009_auto_20151104_1131... OK
taiga-back |   Applying users.0007_auto_20150209_1611... OK
taiga-back |   Applying users.0008_auto_20150213_1701... OK
taiga-back |   Applying users.0009_auto_20150326_1241... OK
taiga-back |   Applying users.0010_auto_20150414_0936... OK
taiga-back |   Applying timeline.0001_initial... OK
taiga-back |   Applying projects.0006_auto_20141029_1040... OK
taiga-back |   Applying projects.0007_auto_20141024_1011... OK
taiga-back |   Applying projects.0008_auto_20141024_1012... OK
taiga-back |   Applying projects.0009_auto_20141024_1037... OK
taiga-back |   Applying projects.0010_project_modules_config... OK
taiga-back |   Applying projects.0011_auto_20141028_2057... OK
taiga-back |   Applying projects.0012_auto_20141210_1009... OK
taiga-back |   Applying projects.0013_auto_20141210_1040... OK
taiga-back |   Applying projects.0014_userstorystatus_is_archived... OK
taiga-back |   Applying projects.0015_auto_20141230_1212... OK
taiga-back |   Applying projects.0016_fix_json_field_not_null... OK
taiga-back |   Applying projects.0017_fix_is_private_for_projects... OK
taiga-back |   Applying projects.0018_auto_20150219_1606... OK
taiga-back |   Applying projects.0019_auto_20150311_0821... OK
taiga-back |   Applying timeline.0002_auto_20150327_1056... OK
taiga-back |   Applying timeline.0003_auto_20150410_0829... OK
taiga-back |   Applying timeline.0004_auto_20150603_1312... OK
taiga-back |   Applying projects.0020_membership_user_order... OK
taiga-back |   Applying projects.0021_auto_20150504_1524... OK
taiga-back |   Applying projects.0022_auto_20150701_0924... OK
taiga-back |   Applying projects.0023_auto_20150721_1511... OK
taiga-back |   Applying projects.0024_auto_20150810_1247... OK
taiga-back |   Applying projects.0025_auto_20150901_1600... OK
taiga-back |   Applying projects.0026_auto_20150911_1237... OK
taiga-back |   Applying projects.0027_auto_20150916_1302... OK
taiga-back |   Applying projects.0028_project_is_featured... OK
taiga-back |   Applying projects.0029_project_is_looking_for_people... OK
taiga-back |   Applying likes.0001_initial... OK
taiga-back |   Applying projects.0030_auto_20151128_0757... OK
taiga-back |   Applying projects.0031_project_logo... OK
taiga-back |   Applying projects.0032_auto_20151202_1151... OK
taiga-back |   Applying projects.0033_text_search_indexes... OK
taiga-back |   Applying projects.0034_project_looking_for_people_note... OK
taiga-back |   Applying projects.0035_project_blocked_code... OK
taiga-back |   Applying projects.0036_project_transfer_token... OK
taiga-back |   Applying projects.0037_auto_20160208_1751... OK
taiga-back |   Applying projects.0038_auto_20160215_1133... OK
taiga-back |   Applying projects.0039_auto_20160322_1157... OK
taiga-back |   Applying projects.0040_remove_memberships_of_cancelled_users_acounts... OK
taiga-back |   Applying projects.0043_auto_20160530_1004... OK
taiga-back |   Applying projects.0044_auto_20160531_1150... OK
taiga-back |   Applying projects.0041_auto_20160519_1058... OK
taiga-back |   Applying projects.0042_auto_20160525_0911... OK
taiga-back |   Applying projects.0045_merge... OK
taiga-back |   Applying issues.0002_issue_external_reference... OK
taiga-back |   Applying issues.0003_auto_20141210_1108... OK
taiga-back |   Applying issues.0004_auto_20150114_0954... OK
taiga-back |   Applying issues.0005_auto_20150623_1923... OK
taiga-back |   Applying issues.0006_remove_issue_watchers... OK
taiga-back |   Applying projects.0046_triggers_to_update_tags_colors... OK
taiga-back |   Applying projects.0047_auto_20160614_1201... OK
taiga-back |   Applying projects.0048_auto_20160615_1508... OK
taiga-back |   Applying projects.0049_auto_20160629_1443... OK
taiga-back |   Applying projects.0050_project_epics_csv_uuid... OK
taiga-back |   Applying projects.0051_auto_20160729_0802... OK
taiga-back |   Applying projects.0052_epic_status... OK
taiga-back |   Applying projects.0053_auto_20160927_0741... OK
taiga-back |   Applying projects.0054_auto_20160928_0540... OK
taiga-back |   Applying projects.0055_json_to_jsonb... OK
taiga-back |   Applying projects.0056_auto_20161110_1518... OK
taiga-back |   Applying contact.0001_initial... OK
taiga-back |   Applying userstories.0012_auto_20160614_1201... OK
taiga-back |   Applying wiki.0001_initial... OK
taiga-back |   Applying wiki.0002_remove_wikipage_watchers... OK
taiga-back |   Applying wiki.0003_auto_20160615_0721... OK
taiga-back |   Applying users.0011_user_theme... OK
taiga-back |   Applying users.0012_auto_20150812_1142... OK
taiga-back |   Applying users.0013_auto_20150901_1600... OK
taiga-back |   Applying users.0014_auto_20151005_1357... OK
taiga-back |   Applying users.0015_auto_20160120_1409... OK
taiga-back |   Applying users.0016_auto_20160204_1050... OK
taiga-back |   Applying users.0017_auto_20160208_1751... OK
taiga-back |   Applying users.0018_remove_vote_issues_in_roles_permissions_field... OK
taiga-back |   Applying users.0019_auto_20160519_1058... OK
taiga-back |   Applying users.0020_auto_20160525_1229... OK
taiga-back |   Applying users.0021_auto_20160614_1201... OK
taiga-back |   Applying users.0022_auto_20160629_1443... OK
taiga-back |   Applying history.0005_auto_20141120_1119... OK
taiga-back |   Applying history.0006_fix_json_field_not_null... OK
taiga-back |   Applying history.0007_set_bloked_note_and_is_blocked_in_snapshots... OK
taiga-back |   Applying history.0008_auto_20150508_1028... OK
taiga-back |   Applying history.0009_auto_20160512_1110... OK
taiga-back |   Applying history.0010_historyentry_project... OK
taiga-back |   Applying history.0011_auto_20160629_1036... OK
taiga-back |   Applying history.0012_auto_20160629_1036... OK
taiga-back |   Applying epics.0001_initial... OK
taiga-back |   Applying epics.0002_epic_color... OK
taiga-back |   Applying custom_attributes.0001_initial... OK
taiga-back |   Applying custom_attributes.0002_issuecustomattributesvalues_taskcustomattributesvalues_userstorycustomattributesvalues... OK
taiga-back |   Applying custom_attributes.0003_triggers_on_delete_customattribute... OK
taiga-back |   Applying custom_attributes.0004_create_empty_customattributesvalues_for_existen_object... OK
taiga-back |   Applying custom_attributes.0005_auto_20150505_1639... OK
taiga-back |   Applying custom_attributes.0006_auto_20151014_1645... OK
taiga-back |   Applying custom_attributes.0007_auto_20160208_1751... OK
taiga-back |   Applying custom_attributes.0008_auto_20160728_0540... OK
taiga-back |   Applying custom_attributes.0009_auto_20160728_1002... OK
taiga-back |   Applying custom_attributes.0010_auto_20160928_0540... OK
taiga-back |   Applying custom_attributes.0011_json_to_jsonb... OK
taiga-back |   Applying custom_attributes.0012_auto_20161201_1628... OK
taiga-back |   Applying custom_attributes.0013_auto_20181022_1624... OK
taiga-back |   Applying custom_attributes.0014_auto_20181025_0711... OK
taiga-back |   Applying djmail.0001_initial... OK
taiga-back |   Applying djmail.0002_auto_20161118_1347... OK
taiga-back |   Applying easy_thumbnails.0001_initial... OK
taiga-back |   Applying easy_thumbnails.0002_thumbnaildimensions... OK
taiga-back |   Applying epics.0003_auto_20160901_1021... OK
taiga-back |   Applying epics.0004_auto_20160928_0540... OK
taiga-back |   Applying epics.0005_epic_external_reference... OK
taiga-back |   Applying external_apps.0001_initial... OK
taiga-back |   Applying external_apps.0002_remove_application_key... OK
taiga-back |   Applying external_apps.0003_auto_20170607_2320... OK
taiga-back |   Applying feedback.0001_initial... OK
taiga-back |   Applying github.0001_initial... OK
taiga-back |   Applying gitlab.0001_initial... OK
taiga-back |   Applying gitlab.0002_auto_20150703_1102... OK
taiga-back |   Applying gogs.0001_initial... OK
taiga-back |   Applying history.0013_historyentry_values_diff_cache... OK
taiga-back |   Applying history.0014_json_to_jsonb... OK
taiga-back |   Applying issues.0007_auto_20160614_1201... OK
taiga-back |   Applying issues.0008_add_due_date... OK
taiga-back |   Applying likes.0002_auto_20151130_2230... OK
taiga-back |   Applying milestones.0002_remove_milestone_watchers... OK
taiga-back |   Applying notifications.0005_auto_20151005_1357... OK
taiga-back |   Applying notifications.0006_auto_20151103_0954... OK
taiga-back |   Applying notifications.0007_notifypolicy_live_notify_level... OK
taiga-back |   Applying notifications.0008_auto_20181010_1124... OK
taiga-back |   Applying projects.0057_auto_20161129_0945... OK
taiga-back |   Applying projects.0058_auto_20161215_1347... OK
taiga-back |   Applying projects.0059_auto_20170116_1633... OK
taiga-back |   Applying projects.0060_auto_20180614_1338... OK
taiga-back |   Applying projects.0061_auto_20180918_1355... OK
taiga-back |   Applying projects.0062_auto_20190826_0920... OK
taiga-back |   Applying references.0001_initial... OK
taiga-back |   Applying sessions.0001_initial... OK
taiga-back |   Applying settings.0001_initial... OK
taiga-back |   Applying tasks.0010_auto_20160614_1201... OK
taiga-back |   Applying tasks.0011_auto_20160928_0755... OK
taiga-back |   Applying tasks.0012_add_due_date... OK
taiga-back |   Applying timeline.0005_auto_20160706_0723... OK
taiga-back |   Applying timeline.0006_json_to_jsonb... OK
taiga-back |   Applying timeline.0007_auto_20170406_0615... OK
taiga-back |   Applying timeline.0008_auto_20190606_1528... OK
taiga-back |   Applying users.0023_json_to_jsonb... OK
taiga-back |   Applying users.0024_auto_20170406_0727... OK
taiga-back |   Applying users.0025_user_uuid... OK
taiga-back |   Applying users.0026_auto_20180514_1513... OK
taiga-back |   Applying users.0027_auto_20180610_2011... OK
taiga-back |   Applying userstorage.0001_initial... OK
taiga-back |   Applying userstorage.0002_fix_json_field_not_null... OK
taiga-back |   Applying userstorage.0003_json_to_jsonb... OK
taiga-back |   Applying userstories.0013_auto_20160722_1018... OK
taiga-back |   Applying userstories.0014_auto_20160928_0540... OK
taiga-back |   Applying userstories.0015_add_due_date... OK
taiga-back |   Applying userstories.0016_userstory_assigned_users... OK
taiga-back |   Applying userstories.0017_userstory_generated_from_task... OK
taiga-back |   Applying votes.0001_initial... OK
taiga-back |   Applying votes.0002_auto_20150805_1600... OK
taiga-back |   Applying webhooks.0001_initial... OK
taiga-back |   Applying webhooks.0002_webhook_name... OK
taiga-back |   Applying webhooks.0003_auto_20150122_1021... OK
taiga-back |   Applying webhooks.0004_auto_20150202_0834... OK
taiga-back |   Applying webhooks.0005_auto_20150505_1639... OK
taiga-back |   Applying webhooks.0006_json_to_jsonb... OK
taiga-back |   Applying wiki.0004_auto_20160928_0540... OK
taiga-back |   Applying wiki.0005_auto_20161201_1628... OK
taiga-back | Trying import local.py settings...
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/fi/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/pl/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/ko/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/en/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/eu/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/nl/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/nb/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/uk/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/tr/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/de/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/zh-Hans/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/he/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/fr/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/ca/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/ja/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/fa/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/es/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/pt_BR/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/ru/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/sv/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/zh-Hant/LC_MESSAGES
taiga-back | processing file django.po in /srv/taiga/back/taiga/locale/it/LC_MESSAGES
taiga-back | Trying import local.py settings...
taiga-back | 
taiga-back | 0 static files copied to '/srv/taiga/back/static', 939 unmodified.
taiga-back | mkdir: can't create directory '/run/nginx': File exists
taiga-back | [2019-11-20 13:40:49 +0000] [37] [INFO] Starting gunicorn 19.9.0
taiga-back | [2019-11-20 13:40:49 +0000] [37] [INFO] Listening at: http://127.0.0.1:8000 (37)
taiga-back | [2019-11-20 13:40:49 +0000] [37] [INFO] Using worker: sync
taiga-back | [2019-11-20 13:40:49 +0000] [45] [INFO] Booting worker with pid: 45
taiga-back | [2019-11-20 13:40:49 +0000] [46] [INFO] Booting worker with pid: 46
taiga-back | [2019-11-20 13:40:49 +0000] [47] [INFO] Booting worker with pid: 47
taiga-back | [2019-11-20 13:40:49 +0000] [48] [INFO] Booting worker with pid: 48
taiga-back | Trying import local.py settings...
taiga-back | Trying import local.py settings...
taiga-back | Trying import local.py settings...
taiga-back | Trying import local.py settings...
taiga-front | 172.23.0.7 - - [20/Nov/2019:13:41:31 +0000] "GET /discover HTTP/1.0" 200 91976 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "172.23.0.1"
taiga-proxy | 172.23.0.1 - - [20/Nov/2019:13:41:31 +0000] "GET /discover HTTP/1.1" 200 91976 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "-"
taiga-front | 172.23.0.7 - - [20/Nov/2019:13:41:31 +0000] "GET /conf.json HTTP/1.0" 200 441 "http://127.0.0.1/discover" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "172.23.0.1"
taiga-proxy | 172.23.0.1 - - [20/Nov/2019:13:41:31 +0000] "GET /conf.json HTTP/1.1" 200 441 "http://127.0.0.1/discover" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "-"
taiga-proxy | 172.23.0.1 - - [20/Nov/2019:13:41:31 +0000] "GET /v-1569907893851/images/favicon.png HTTP/1.1" 200 6979 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "-"
taiga-front | 172.23.0.7 - - [20/Nov/2019:13:41:31 +0000] "GET /v-1569907893851/images/favicon.png HTTP/1.0" 200 6979 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "172.23.0.1"
taiga-front | 172.23.0.7 - - [20/Nov/2019:13:41:34 +0000] "GET /conf.json HTTP/1.0" 200 441 "http://localhost/" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "172.23.0.1"
taiga-proxy | 172.23.0.1 - - [20/Nov/2019:13:41:34 +0000] "GET /conf.json HTTP/1.1" 200 441 "http://localhost/" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "-"
taiga-proxy | 172.23.0.1 - - [20/Nov/2019:13:41:34 +0000] "GET /v-1569907893851/fonts/OpenSans-Regular.ttf HTTP/1.1" 499 0 "http://localhost/v-1569907893851/styles/theme-taiga.css" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "-"
taiga-front | 172.23.0.7 - - [20/Nov/2019:13:41:34 +0000] "GET /v-1569907893851/fonts/OpenSans-Regular.ttf HTTP/1.0" 200 0 "http://localhost/v-1569907893851/styles/theme-taiga.css" "Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0" "172.23.0.1"

This is result:

How to troubleshoot issues ?

Hello !
Thanks a lot for the images, they seem to really clean. Although, I integrated taiga-back, taiga-front, taiga-db, taiga-events and taiga-rabbit in my existing docker-compose file (as I already have other services running, such as gitlab and a nginx reverse proxy, which is why I didn't keep the original taiga-proxy from your docker-compose file.

After running it, I get to the Taiga home page, but it says: Something happened and our Oompa Loompas are working on it.

Where can I find the logs that would help me to understand what I did wrong ?

Cheers.

FATAL: data directory "/var/lib/postgresql/data" has wrong ownership

git clone https://github.com/docker-taiga/taiga.git

or

git clone --depth=1 -b latest https://github.com/docker-taiga/taiga.git

cd .\taiga\

docker-compose up

taiga-db  | creating configuration files ... ok
taiga-db  | 2018-12-04 06:56:29.262 UTC [47] FATAL:  data directory "/var/lib/postgresql/data" has wrong ownership
taiga-db  | 2018-12-04 06:56:29.262 UTC [47] HINT:  The server must be started by the user that owns the data directory.
taiga-db  | child process exited with exit code 1

docker-compose run db ls -la /var/lib/postgresql/data/

total 8
drwxrwxrwx    1 1000     50            4096 Dec  4 07:00 .
drwxr-xr-x    3 postgres postgres      4096 Nov  9 23:15 ..

Postgre database maxed out at 100MB

Dear docker-taiga,

Thanks as ever for providing this great package. I have been running it for 2 years without problems.

However, unfortunately our server has stopped working, and it appears that the database cannot write any more:

docker-compose logs -t db
taiga-db  | 2020-06-17T08:55:22.362237520Z 2020-06-17 08:55:22.362 UTC [8917] LOG:  could not close temporary statistics file "pg_stat_tmp/global.tmp": No space left on device
taiga-db  | 2020-06-17T08:55:23.012867079Z 2020-06-17 08:55:23.012 UTC [8917] LOG:  could not close temporary statistics file "pg_stat_tmp/global.tmp": No space left on device

The db takes up exactly 100MB... is the size limited somewhere?

sudo du -h --max-depth=0 data/db
100M    data/db

Thanks in advance!

Add .idea/ files to .gitignore

Update containers for Taiga 4.2.12

Hi,
The most current version of your container seem te be compiled 7 months ago. Any change you could update them for the newest taiga versions?

Thanks for effort. Greatly appreciating your work.

Celery worker is missing

Hi,

Thanks a lot for the setup!

As the composition is defined, there is no celery worker to take the asynchronous tasks sent by the back container through the redis one. As a result, for example, the timelines of the projects are not updated automatically.

If we agree on this fact, I could provide a PR.

Collapse 2 parameters TAIGA_HOST and TAIGA_HOSTNAME into one?

Can't upload >1MB file

If I try to upload file that is over 1MB (under 1MB it works) I get nginx error: client intended to send too large body.
To solve this issue I modified my nginx.conf to include this in a server section:

	client_max_body_size 100m;
	client_body_buffer_size 50m;

The effect of such modification is that nginx no longer responds with error but file upload for files >1MB is still not working. Is there anything I can do about it? In docker-compose logs there are no hints (no error messages).

The docker-compose up stuck at Trying import local.py

I have tried to use docker-compose to run the Taica, I use the docker-compose file and the variable.env as given in the Github. However, I have changed the TAIGA_HOST value to my URL.
and when I start the containers using the docker-compose up. I always stuck to this error. I have tried on my computer, and my AWS EC2 and it returns the same result.

Upgrade to v6

Firstly, thanks for your work.

Please could you upgrade to v6.

Thanks.

No documented default admin credentials.

I've gotten a tryout instance up and running but there doesn't appear to be any documentation on how to create initial users or what the default credentials are despite finding admin and 123123 for the password documented randomly.

LDAP authentification

Hi all,

thanks for the great docker images!
I was wondering if anyone has already implemented the ldap-authentification with these images?

Email settings in variables.env

Having example email variables shown in the variables.env file would make configuration a bit easier for users not familiar with the taiga variables required.

## email details (SMTP example)
#DEFAULT_FROM_EMAIL = '[email protected]'
#CHANGE_NOTIFICATIONS_MIN_INTERVAL = 30 #seconds
#EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
#EMAIL_USE_TLS = True
#EMAIL_USE_SSL = False
#EMAIL_HOST = 'smtp.example.net'
#EMAIL_PORT = 587
#EMAIL_HOST_USER = '[email protected]'
#EMAIL_HOST_PASSWORD = 'PASSWORD'

Problem with TAIGA_HOST env variable.

Hi.

I just cloned your repository to start taiga on my VPS.
Once i figured out that TAIGA_HOST was not modified in the container.
I tried to change it in the file variables.env.

So i tried to set the variable directly in the compose file.
Everything is working fine now, you did a good job.
However, is it possible that when i change the variable in the env file, the TAIGA_HOST in the container is also changed, rather than adding an env variable in the compose file ?

 front:
    image: dockertaiga/front:5.0.7
    container_name: taiga-front
    restart: unless-stopped
    networks:
      - default
    volumes:
      - ./conf/front:/taiga-conf
    environment:
    - TAIGA_HOST=taiga.mydomain.com
    env_file:
      - variables.env

Add gitlab auth provider

It would be good to have gitlab auth available in the docker version.
It would require integrating the changes shown here, which should be possible to add to taiga-front and taiga-back Dockerfiles.

Using TAIGA_PORT kinda breaks it all

Title says it all.

I was able to run the docker-compose.yml easily on localhost without changing anything, but setting TAIGA_PORT to anything else than 80 breaks a lot of things. It is also unclear what should be changed in docker-compose.yml to accomodate for it.

Shouldn’t just changing the proxy port from 80:80 to 8080:80 be sufficient? I tried but was then stuck on the error page.

Thanks!

Thanks for a great product... after having issues with other taiga docker releases I have every feature working with a minimum of effort.

Environmentalize public user registration

There's a slur of parameters that can be configured in the variables.env, but there's no way to enable public registration without rebuilding the docker images for front and back. The variable is PUBLIC_REGISTER_ENABLED in the taiga-back conf and publicRegisterEnabled in the taiga-front conf.

This should be quick and easy. I'll gladly submit a PR if that's easier.

Websocket load from https

Hi,
I set the env variable ENABLE_SSL to yes and the application is blocked by chrome because it tried to load unsecured script and pages from a secured one.
I have a server with ubuntu using apache vhost with proxypass to redirect to my docker container.
Here is the chrome console error :
Mixed Content: The page at 'https://taiga.mydomain.com/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://taiga.mydomain.com/events/'. This request has been blocked; this endpoint must be available over WSS.
Here is my apache vhost configuration :

<VirtualHost *:80>
    ServerName taiga.mydomain.com
    ServerAdmin [email protected]

    Redirect / https://taiga.mydomain.com/
</VirtualHost>

<VirtualHost *:443>
    ServerName taiga.mydomain.com
    ServerAdmin [email protected]

    Header Set X-Robots-Tag "noindex, nofollow, noarchive, nosnippet"

    SSLProxyEngine On
    ProxyPreserveHost On
    ProxyPass         / https://localhost:3002/
    ProxyPassReverse  / https://localhost:3002/
    ProxyPass         /events wss://localhost:3002/events

    ErrorLog ${APACHE_LOG_DIR}/taiga_error.log
    CustomLog ${APACHE_LOG_DIR}/taiga_access.log combined

    SSLCertificateFile /etc/letsencrypt/live/taiga.mydomain.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/taiga.mydomain.com/privkey.pem
    Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>

Obviously my own domain was replaced by "mydomain".

Any idea ?
Thanks

Email support?

Hi,
Are there some env variables to set so we can use emails?
I did not find how to get emails to work.
Thx a lot for the great work!

Will this ever finish?

Apache configuration

Hi,
First of all I'm not used to Nginx, I have a debian server with apache2 server who reverse proxy to taiga docker container with Nginx.
SSL is enable.
It works for front but webservice and back doesn't.
I have a 406 code for websocket and 502 for the back.
Here is the console error reporting :

Error

GET https://taiga.mydomain.com/api/v1/stats/discover 502 (Bad Gateway)
GET https://taiga.mydomain.com/api/v1/projects?discover_mode=true&order_by=-total_fans_last_week 502 (Bad Gateway)
GET https://taiga.mydomain.com/api/v1/projects?discover_mode=true&order_by=-total_activity_last_week 502 (Bad Gateway)
GET https://taiga.mydomain.com/api/v1/projects?discover_mode=true&is_featured=true 502 (Bad Gateway)
WebSocket connection to 'wss://taiga.mydomain.com/events/' failed: Error during WebSocket handshake: Unexpected response code: 426

Here is my Apache configuration :

mydomain.conf

<VirtualHost *:80>
    ServerName taiga.mydomain.com
    ServerAdmin [email protected]

    Redirect / https://taiga.mydomain.com/
</VirtualHost>

<VirtualHost *:443>
    ServerName taiga.mydomain.com
    ServerAdmin [email protected]

    Header Set X-Robots-Tag "noindex, nofollow, noarchive, nosnippet"

    SetOutputFilter SUBSTITUTE,DEFLATE

    SSLProxyEngine On
    ProxyPreserveHost On
    ProxyPass         / https://localhost:3002/
    ProxyPassReverse  / https://localhost:3002/

    AddOutputFilterByType SUBSTITUTE text/html
    Substitute "s|https://localhost:3002/|https://taiga.mydomain.com/|i"

    ErrorLog ${APACHE_LOG_DIR}/taiga_error.log
    CustomLog ${APACHE_LOG_DIR}/taiga_access.log combined

    SSLCertificateFile /etc/letsencrypt/live/taiga.mydomain.com/fullchain.pem
    SSLCertificateKeyFile /etc/letsencrypt/live/taiga.mydomain.com/privkey.pem
    Include /etc/letsencrypt/options-ssl-apache.conf
    <Proxy *>
        Order deny,allow
        Allow from all
        Allow from localhost
    </Proxy>
</VirtualHost>

Here is my Nginx configuration :

nginx.conf

server {
	server_name taiga.mydomain.com;
	listen 80;
	location / {
		return 302 https://$server_name$request_uri;
	}
}

server {
	server_name taiga.mydomain.com;
	listen 443 ssl;
	ssl_certificate /taiga-cert/fullchain.pem;
	ssl_certificate_key /taiga-cert/privkey.pem;

	location ^~ /events {
		proxy_pass http://events:8888/;
		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;
	}

	location ^~ /api {
		include proxy_params;
		proxy_pass http://back;
	}

	location ^~ /admin {
		include proxy_params;
		proxy_pass http://back;
	}

	location ^~ /static {
		include proxy_params;
		proxy_pass http://back;
	}

	location ^~ /media {
		include proxy_params;
		proxy_pass http://back;
	}

	location / {
		include proxy_params;
		proxy_pass http://front;
	}
}

And here is the docker compose configuration :

docker-compose.yml

version: '3'

services:
  back:
    image: dockertaiga/back
    container_name: taiga-back
    restart: unless-stopped
    depends_on:
      - db
      - events
    networks:
      - default
    volumes:
      - ./data/media:/taiga-media
      - ./conf/back:/taiga-conf
    env_file:
      - variables.env

  front:
    image: dockertaiga/front
    container_name: taiga-front
    restart: unless-stopped
    networks:
      - default
    volumes:
      - ./conf/front:/taiga-conf
    env_file:
      - variables.env

  db:
    image: postgres:11-alpine
    container_name: taiga-db
    restart: unless-stopped
    networks:
      - default
    env_file:
      - variables.env
    volumes:
      - ./data/db:/var/lib/postgresql/data

  rabbit:
    image: dockertaiga/rabbit
    container_name: taiga-rabbit
    restart: unless-stopped
    networks:
      - default
    env_file:
      - variables.env

  events:
    image: dockertaiga/events
    container_name: taiga-events
    restart: unless-stopped
    depends_on:
      - rabbit
    networks:
      - default
    env_file:
      - variables.env

  proxy:
    image: dockertaiga/proxy
    container_name: taiga-proxy
    restart: unless-stopped
    depends_on:
      - back
      - front
      - events
    networks:
      - default
    ports:
      - 3002:443
      - 3003:80
    volumes:
      - /etc/letsencrypt/live/taiga.mydomain.com/:/taiga-cert
      - /etc/letsencrypt/archive/:/archive
      - ./conf/proxy:/taiga-conf
    env_file:
      - variables.env

networks:
  default:

Any ideas ?