Fix critical port conflict: move portfolio off Gitea's port 3000
deploy / deploy (push) Successful in 12s
deploy / deploy (push) Successful in 12s
Host port 3000 is Gitea (git.soroushasadi.com proxies to :3000). The portfolio was publishing 3000:3000 AND the deploy had a "Free Port 3000" step that force-removed every container on :3000 — which evicted the Gitea container. - compose: publish 3020:3000 instead of 3000:3000 - deploy: delete the "Free Port 3000" step entirely; compose recreates only our own named container and must never touch other stacks Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
+3
-1
@@ -11,8 +11,10 @@ services:
|
||||
image: soroushasadi-site:latest
|
||||
container_name: soroushasadi-site
|
||||
restart: unless-stopped
|
||||
# Host port 3020 → container 3000. Port 3000 on the host is Gitea
|
||||
# (git.soroushasadi.com proxies to :3000) — NEVER publish on 3000.
|
||||
ports:
|
||||
- "3000:3000"
|
||||
- "3020:3000"
|
||||
environment:
|
||||
ASPNETCORE_ENVIRONMENT: Production
|
||||
DataDir: /data
|
||||
|
||||
Reference in New Issue
Block a user