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
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 Thanks for telling us!
We have fixed our CI/CD template (https://github.com/elestio-examples/zammad) and we are going to fix as well the dedicated service template in the next 2 days
@lclc Auto-update is done only on Sunday night by default, this can be adjusted in the service dashboard, there you can also do an UPDATE NOW
About latest ... when deploying a new service we give the user opportunity to select a specific version in the dropdown. Since it's rapidly changing, by default we keep latest selected. But indeed for a production system we recommend to fix the major version using tag "5" for eg
Hey @VISIGO,
We have in our roadmap a feature to be able to generate additional access to nebula, but it's not yet ready in the UI.
Feel free to open a ticket in Elestio dashboard and we can do it for you manually and provide instructions
Please indicate your Elestio project and OS for the client
@lclc just wanted to confirm the issue is now fixed on Firefox
@lclc strange on my side I'm able to see this correctly on your service:
I'll check with our dev team about this, it's probably a frontend JS missdisplaying the date