@jbenguira Yes, it's fixed now for Firefox, thanks!

Best posts made by lclc
-
RE: Automated remote backups (Borg): Where are they stored?
Latest posts made by lclc
-
RE: Zammad default Docker-Compose uses 'latest'
@jbenguira great. Can you let me know or is there a way to see when it's updated without creating a new instance?
-
RE: Zammad default Docker-Compose uses 'latest'
@jbenguira but that one still has
image: ${IMAGE_REPO}:zammad-postgresql-${SOFTWARE_VERSION_TAG}
instead of
image: postgres:${POSTGRES_VERSION}
(taken from GitHub https://github.com/elestio-examples/zammad/blob/main/docker-compose.yml#L16)
-
RE: Zammad default Docker-Compose uses 'latest'
@jbenguira how can I check when the new docker-compose (service template) is up without creating a new VM?
-
RE: Zammad default Docker-Compose uses 'latest'
@jbenguira sounds good. FYI your link points to a private GitHub repo.
-
RE: Zammad default Docker-Compose uses 'latest'
Ah yes, see this commit on November 4th: https://github.com/zammad/zammad-docker-compose/commit/c5c1db541a05f18480169490ee92146a8883a3b8#diff-e45e45baeda1c1e73482975a664062aa56f20c03dd9d64a827aba57775bed0d3
They are using the upstream postgres images now.
Probably best to track their https://github.com/zammad/zammad-docker-compose/releases, which are independent of the zammad releases.
-
RE: Zammad default Docker-Compose uses 'latest'
I guess I picked 'latest' here when I set it up, but it's a bit messy, showing all the tags.
I assume it comes from their messy Docker repository (https://hub.docker.com/r/zammad/zammad-docker-compose/tags).
When I click UPDATE NOW it stays on 5.2.3 (which was probably the latest when I set it up), even though it has 'latest' set as SOFTWARE_VERSION_TAG in the ENV file.
I've now cloned my existing instance and choose stable, but the docker-compose doesn't work with stable because there aren't images tagged as stable for all the backend images of zammad in there (e.g. there is no zammad-postgresql-stable)
The latest image of zammad-postgresql- is zammad-postgresql-5.2.3-32 (2 months ago). It looks like they discontinued publishing those, which means the docker-compose file from Elestio doesn't work anymore.
-
Zammad default Docker-Compose uses 'latest'
The Zammad from elest.io uses
SOFTWARE_VERSION_TAG=latest
in the .env for the docker-compose. In the Zammad docs it says
Never use the latest tag. Use a tag which has a version attached.
(see https://docs.zammad.org/en/latest/install/docker-compose.html)
However, even with auto-update on I currently have version 5.2.3 installed through elest.io. But the current 'latest'-tag points to 5.3.0-30 (see
https://hub.docker.com/r/zammad/zammad-docker-compose/tags).Two questions:
- Any idea why it's not updating to the actual latest?
- Should it maybe not point to latest like it says in the docs?
I'd like to have automated security updates for both the OS (as it's default with Elestio) and the software. But not automated major-updates because I'm afraid it might just break my production system.
-
RE: Automated remote backups (Borg): Where are they stored?
@jbenguira Yes, it's fixed now for Firefox, thanks!
-
RE: Automated remote backups (Borg): Where are they stored?
@jbenguira Thanks for checking. I tested with Chrome: There it works. But in Firefox it says "Invalid Date".
-
RE: Automated remote backups (Borg): Where are they stored?
@jbenguira Thank you. Good to know.
I assume the instances ID is 25536560 (taken from the URL).