atfatmc/AdamuSw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
145 Commits 7 Branches 0 Tags
797e17b666bee822f41cc99a0ad1b2869e4e40a4
Commit Graph

3 Commits

Author SHA1 Message Date
Acentech Dev
797e17b666 Pin the production image to the Castle Siege release (d249fca935)
Some checks failed
.NET Core / build (push) Has been cancelled
Details 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 2026-08-04 21:53:09 +03:00
Acentech Dev
0fdb455cec Pin the production image to a commit-SHA tag instead of :latest
Some checks failed
.NET Core / build (push) Has been cancelled
Details 
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>
 2026-07-31 15:37:42 +03:00
Acentech Dev
2e59cdfe1f chore: AdamuSw deploy composes (local test + Coolify/Traefik prod) using self-built image
Some checks failed
.NET Core / build (push) Has been cancelled
Details 
- deploy-adamu/docker-compose.local.yml: local postgres + adamu-openmu:dev, direct 8080
- deploy-adamu/docker-compose.prod.yml: Coolify/Traefik prod adapted from AdaMu, image swapped to our build
- additive folder (deploy-adamu) to avoid upstream deploy/ merge conflicts
- plan Step5 fixed (-p:ci=true), paths -> deploy-adamu

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-07-14 19:31:07 +03:00