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) <noreply@anthropic.com>

.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.
+      # It joins the `proxy` network (the one Nginx Proxy Manager is on), so
-      #   Point Nginx Proxy Manager's proxy host at:  <server-ip>:8080
+      # NPM can reach it by container name — no published host port needed.
-      #   (Or, if NPM runs in Docker, put this container on NPM's network and
+      # In NPM, forward to:  hostname = altricade-portfolio , port = 80 , http
-      #    forward to  altricade-portfolio:80  instead — see note below.)
       - 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.