Fix docker-compose to use Gitea registry image; v1.1.41

docker-compose.yml was still pointing to the old GHCR image
(ghcr.io/nmemmert/siteforge:latest) after CI was switched to push
to git.necloud.us/nate/siteforge:latest, so servers were pulling
a stale build that predated the download/header changes.

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

.github/workflows/docker-publish.yml

@@ -36,18 +36,18 @@ jobs:
       - name: Run production build
         run: npm run build
 
-      - name: Log in to GHCR
+      - name: Log in to Gitea Container Registry
         uses: docker/login-action@v3
         with:
-          registry: ghcr.io
+          registry: git.necloud.us
-          username: ${{ github.actor }}
+          username: ${{ secrets.REGISTRY_USER }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          password: ${{ secrets.REGISTRY_TOKEN }}
 
       - name: Extract metadata
         id: meta
         uses: docker/metadata-action@v5
         with:
-          images: ghcr.io/nmemmert/siteforge
+          images: git.necloud.us/nate/siteforge
           tags: |
             type=raw,value=latest,enable={{is_default_branch}}
             type=sha

docker-compose.yml

@@ -1,6 +1,6 @@
 services:
   portfolio:
-    image: ghcr.io/nmemmert/siteforge:latest
+    image: git.necloud.us/nate/siteforge:latest
     pull_policy: always
     container_name: siteforge-app
     ports:

package.json

@@ -1,7 +1,7 @@
 {
   "name": "siteforge",
   "private": true,
-  "version": "1.1.40",
+  "version": "1.1.41",
   "type": "module",
   "scripts": {
     "dev": "vite",