Pin the production image to a commit-SHA tag instead of :latest
Some checks failed
.NET Core / build (push) Has been cancelled

Coolify does not re-pull a tag it already knows locally, so :latest silently
kept the server on a stale layer. On 2026-07-31 production was still running
the 26 July image while DockerHub :latest pointed at a newer digest, which is
why update 104 never appeared in the admin panel.

A commit-SHA tag has never been seen by the host, so the pull is unavoidable.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Acentech Dev
2026-07-31 15:37:42 +03:00
parent 452f0bb139
commit 0fdb455cec

View File

@@ -4,7 +4,12 @@
# set edilirse onu, edilmezse aşağıdaki default'u kullanır.
services:
openmu-startup:
image: ${OPENMU_IMAGE:-atfatmc/adamu-openmu:latest} # <-- kendi DockerHub image'imiz (Task 3)
# Production'da DAIMA commit-SHA etiketi kullanilir, asla :latest. :latest degisken
# bir isim oldugu icin Coolify onu yerelde tanidiginda yeniden cekmez ve eski katman
# sessizce calismaya devam eder (2026-07-31'de tam olarak bu oldu: sunucu 26 Temmuz
# image'ini calistiriyordu). SHA etiketi daha once gorulmedigi icin pull zorunlu olur.
# Yeni surum yayinlarken bu satiri yeni SHA ile guncelle.
image: ${OPENMU_IMAGE:-atfatmc/adamu-openmu:452f0bb139de}
container_name: openmu-startup
networks:
- coolify