Fix: Configurazione registry HTTP locale per evitare Cloudflare

- Aggiunto env REGISTRY: 192.168.1.37:30008 per bypassare Cloudflare
- Configurato buildx per supportare HTTP insecure sul registry locale
- Aggiornato docker meta per usare registry IP diretto
- Modificato login per autenticarsi su 192.168.1.37:30008
- Risolto errore 413 Payload Too Large causato da Cloudflare

.gitea/workflows/docker-build.yml

@@ -13,6 +13,10 @@ on:
       - main
       - master
 
+env:
+  REGISTRY: 192.168.1.37:30008
+  IMAGE_NAME: ${{ github.repository }}
+
 jobs:
   build-and-push:
     runs-on: ubuntu-latest
@@ -36,7 +40,7 @@ jobs:
             image=moby/buildkit:latest
             network=host
           config-inline: |
-            [registry."gitea.home-nas-ds.org"]
+            [registry."192.168.1.37:30008"]
               http = true
               insecure = true
 
@@ -45,7 +49,7 @@ jobs:
         uses: docker/metadata-action@v4
         with:
           images: |
-            gitea.home-nas-ds.org/${{ github.repository }}
+            ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
           tags: |
             type=ref,event=branch
             type=ref,event=pr
@@ -62,7 +66,7 @@ jobs:
           cat > ~/.docker/config.json << EOF
           {
             "auths": {
-              "gitea.home-nas-ds.org": {
+              "192.168.1.37:30008": {
                 "auth": "$AUTH"
               }
             }