administrators

FYI we have added today ability to cancel queued CICD jobs ️

@VISIGO It's currently not possible to cancel a build in-progress, but will check with our team to add this soon

@sam_uk thanks for suggesting it, I have added it to our roadmap

Hey @dj,
It should be transparent, since the new docker cli is also compatible with an alias to the old one. So we will continue to use the old syntaxe docker-compose.

Hey @dj, thanks for the suggestion, I'll pass it to our team

Hey @mane, unfortunately Graylog license is SSPL (https://github.com/Graylog2/graylog2-server/blob/master/LICENSE)

So we are not allowed to offer it directly on Elestio, you can still use our CICD system to deploy it yourself in Elestio

@VISIGO Thanks for the suggestion, will be added soon to our catalog

@lclc you are right, we are in the process of unifying with the Git repos,
this will be done soon for Zamad

@lclc here it is

version: '3.3'
services:

  zammad-backup:
    command: ["zammad-backup"]
    depends_on:
      - zammad-railsserver
    entrypoint: /usr/local/bin/backup.sh
    environment:
      - BACKUP_SLEEP=86400
      - HOLD_DAYS=10
      - POSTGRESQL_USER=${POSTGRES_USER}
      - POSTGRESQL_PASSWORD=${SOFTWARE_PASSWORD}
    image: ${IMAGE_REPO}:zammad-postgresql-${SOFTWARE_VERSION_TAG}
    links:
      - zammad-postgresql
    restart: ${RESTART}
    volumes:
      - ./zammad_backup:/var/tmp/zammad
      - ./zammad_data:/opt/zammad

  zammad-elasticsearch:
    environment:
      - discovery.type=single-node
    image: ${IMAGE_REPO}:zammad-elasticsearch-${SOFTWARE_VERSION_TAG}
    restart: ${RESTART}
    volumes:
      - ./elasticsearch_data:/usr/share/elasticsearch/data

  zammad-init:
    command: ["zammad-init"]
    depends_on:
      - zammad-postgresql
    environment:
      - POSTGRESQL_USER=${POSTGRES_USER}
      - POSTGRESQL_PASS=${SOFTWARE_PASSWORD}
    image: ${IMAGE_REPO}:zammad-${SOFTWARE_VERSION_TAG}
    links:
      - zammad-elasticsearch
      - zammad-postgresql
    restart: on-failure
    volumes:
      - ./zammad_data:/opt/zammad

  zammad-memcached:
    command: memcached -m 256M
    image: memcached:1.6.9-alpine
    restart: ${RESTART}

  zammad-nginx:
    command: ["zammad-nginx"]
    ports:
      - "172.17.0.1:8080:8080"
    depends_on:
      - zammad-railsserver
    image: ${IMAGE_REPO}:zammad-${SOFTWARE_VERSION_TAG}
    environment:
      - NGINX_SERVER_SCHEME=https
    links:
      - zammad-railsserver
      - zammad-websocket
    restart: ${RESTART}
    volumes:
      - ./zammad_data:/opt/zammad

  zammad-postgresql:
    environment:
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${SOFTWARE_PASSWORD}
    image: ${IMAGE_REPO}:zammad-postgresql-${SOFTWARE_VERSION_TAG}
    restart: ${RESTART}
    volumes:
      - ./postgresql_data:/var/lib/postgresql/data

  zammad-railsserver:
    command: ["zammad-railsserver"]
    depends_on:
      - zammad-memcached
      - zammad-postgresql
    image: ${IMAGE_REPO}:zammad-${SOFTWARE_VERSION_TAG}
    links:
      - zammad-elasticsearch
      - zammad-memcached
      - zammad-postgresql
    restart: ${RESTART}
    volumes:
      - ./zammad_data:/opt/zammad

  zammad-scheduler:
    command: ["zammad-scheduler"]
    depends_on:
      - zammad-memcached
      - zammad-railsserver
    image: ${IMAGE_REPO}:zammad-${SOFTWARE_VERSION_TAG}
    links:
      - zammad-elasticsearch
      - zammad-memcached
      - zammad-postgresql
    restart: ${RESTART}
    volumes:
      - ./zammad_data:/opt/zammad

  zammad-websocket:
    command: ["zammad-websocket"]
    depends_on:
      - zammad-memcached
      - zammad-railsserver
    image: ${IMAGE_REPO}:zammad-${SOFTWARE_VERSION_TAG}
    links:
      - zammad-postgresql
      - zammad-memcached
    restart: ${RESTART}
    volumes:
      - ./zammad_data:/opt/zammad

@lclc Indeed, fixed now