From bff28a8d0f332a3f06f0bac05128731aa9c8fbe8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=97=D0=B0=D0=B8=D0=B4=20=D0=9E=D0=BC=D0=B0=D1=80=20?= =?UTF-8?q?=D0=9C=D0=B5=D0=B4=D1=85=D0=B0=D1=82=20=7C=20Zaid=20Omar=20Medh?= =?UTF-8?q?at?= Date: Thu, 9 Jul 2026 12:38:15 +0500 Subject: [PATCH] ci: run app container on the proxy network for NPM Attach altricade-portfolio to the existing 'proxy' network so Nginx Proxy Manager reaches it by container name (altricade-portfolio:80), no host port. Co-Authored-By: Claude Opus 4.8 (1M context) --- .forgejo/workflows/deploy.yml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/.forgejo/workflows/deploy.yml b/.forgejo/workflows/deploy.yml index b3c0ea1..87d0c56 100644 --- a/.forgejo/workflows/deploy.yml +++ b/.forgejo/workflows/deploy.yml @@ -33,17 +33,16 @@ jobs: docker build -t altricade-portfolio:${{ github.sha }} -t altricade-portfolio:latest . # Replace the running container with the freshly built image. - # -p 8080:80 publishes the container on host port 8080. - # Point Nginx Proxy Manager's proxy host at: :8080 - # (Or, if NPM runs in Docker, put this container on NPM's network and - # forward to altricade-portfolio:80 instead — see note below.) + # It joins the `proxy` network (the one Nginx Proxy Manager is on), so + # NPM can reach it by container name — no published host port needed. + # In NPM, forward to: hostname = altricade-portfolio , port = 80 , http - name: Deploy container run: | docker rm -f altricade-portfolio 2>/dev/null || true docker run -d \ --name altricade-portfolio \ --restart unless-stopped \ - -p 8080:80 \ + --network proxy \ altricade-portfolio:latest # Free disk on the shared runner by dropping old, untagged images.