soroush.asadi e4ad440c15 fix(ci): stop & remove old container before deploying new one ...

docker compose up --force-recreate only works when Compose owns the
container. If the container was started outside Compose (e.g. manually
via docker restart), Compose can't recreate it and errors with
"container name already in use". Explicitly stopping and removing it
first handles both cases cleanly.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-06-02 01:59:16 +03:30

.claude

first commit

2026-05-31 00:42:08 +03:30

.gitea/workflows

fix(ci): stop & remove old container before deploying new one

2026-06-02 01:59:16 +03:30

admin

first commit

2026-05-31 00:42:08 +03:30

deploy

first commit

2026-05-31 00:42:08 +03:30

DrSousan.Api

fix: render before/after gallery images from API with tab filtering

2026-06-01 23:59:57 +03:30

.dockerignore

first commit

2026-05-31 00:42:08 +03:30

.env.example

first commit

2026-05-31 00:42:08 +03:30

.gitignore

first commit

2026-05-31 00:42:08 +03:30

blog.html

first commit

2026-05-31 00:42:08 +03:30

DEPLOY.md

first commit

2026-05-31 00:42:08 +03:30

docker-compose.yml

fix: lock compose project name to 'drsousan', fix mirrors typo in image ref

2026-05-31 23:41:20 +03:30

index.html

fix: render before/after gallery images from API with tab filtering

2026-06-01 23:59:57 +03:30

post.html

first commit

2026-05-31 00:42:08 +03:30

start.bat

first commit

2026-05-31 00:42:08 +03:30

S

Description

No description provided

1.3 MiB

Languages

HTML 74.2%

C# 25.4%

Dockerfile 0.3%

Batchfile 0.1%