feat(docker): aggiunge supporto immagini multi-architettura arm64 e amd64 con manifest workflow per build e push

Author: strawberry-code

.claude/commands/build.md

@@ -1,6 +1,6 @@
-# Build Immagini Docker
+# Build Immagini Docker Multi-Architettura
 
-Builda le immagini Docker per linux/amd64 (compatibile con server cloud).
+Builda le immagini Docker per linux/amd64 (Ubuntu/cloud) e linux/arm64 (Mac M1/M2).
 
 ## Sintassi
 
@@ -34,34 +34,63 @@ Chiedi all'utente quale variante buildare:
 - `tika` - Dockerfile.tika (con Tika per PDF, ~4GB)
 - `both` - Entrambe
 
-### Step 3: Esegui build
+### Step 3: Esegui build multi-arch
 
-**Per variante base:**
+Per ogni variante, builda entrambe le architetture.
+
+**Build arm64 (nativo su Mac, veloce):**
 ```bash
-podman build --platform linux/amd64 \
-  -t ghcr.io/strawberry-code/ragify:{version} \
-  -t ghcr.io/strawberry-code/ragify:latest \
-  -f Dockerfile .
+podman build --platform linux/arm64 \
+  -t ghcr.io/strawberry-code/ragify:{version}-tika-arm64 \
+  -f Dockerfile.tika .
 ```
 
-**Per variante tika:**
+**Build amd64 (emulato su Mac, lento ~10 min):**
 ```bash
 podman build --platform linux/amd64 \
-  -t ghcr.io/strawberry-code/ragify:{version}-tika \
-  -t ghcr.io/strawberry-code/ragify:latest-tika \
+  -t ghcr.io/strawberry-code/ragify:{version}-tika-amd64 \
   -f Dockerfile.tika .
 ```
 
-### Step 4: Verifica
+**NOTA:** Le due build possono essere eseguite in parallelo per risparmiare tempo.
+
+### Step 4: Crea manifest multi-arch
+
+```bash
+# Rimuovi manifest esistente se presente
+podman manifest rm ghcr.io/strawberry-code/ragify:{version}-tika 2>/dev/null || true
+
+# Crea nuovo manifest
+podman manifest create ghcr.io/strawberry-code/ragify:{version}-tika
+
+# Aggiungi le immagini
+podman manifest add ghcr.io/strawberry-code/ragify:{version}-tika \
+  ghcr.io/strawberry-code/ragify:{version}-tika-arm64
+
+podman manifest add ghcr.io/strawberry-code/ragify:{version}-tika \
+  ghcr.io/strawberry-code/ragify:{version}-tika-amd64
+
+# Crea anche manifest per latest
+podman manifest rm ghcr.io/strawberry-code/ragify:latest-tika 2>/dev/null || true
+podman manifest create ghcr.io/strawberry-code/ragify:latest-tika
+podman manifest add ghcr.io/strawberry-code/ragify:latest-tika \
+  ghcr.io/strawberry-code/ragify:{version}-tika-arm64
+podman manifest add ghcr.io/strawberry-code/ragify:latest-tika \
+  ghcr.io/strawberry-code/ragify:{version}-tika-amd64
+```
+
+### Step 5: Verifica
 
 ```bash
 podman images | grep ragify
+podman manifest inspect ghcr.io/strawberry-code/ragify:{version}-tika
 ```
 
-### Step 5: Output
+### Step 6: Output
 
 Mostra:
-- Tag creati
+- Tag creati per entrambe le architetture
+- Manifest multi-arch creati
 - Dimensione immagini
 - Prossimo comando: `/push-ghcr` o `/push-ghcr {version}`
 
@@ -70,20 +99,23 @@ Mostra:
 ## Esempio
 
 ```
-/build 1.1.0
+/build 1.1.3
 
-Building ragify:1.1.0-tika...
-✓ ghcr.io/strawberry-code/ragify:1.1.0-tika
-✓ ghcr.io/strawberry-code/ragify:latest-tika
+Building ragify:1.1.3-tika (arm64 + amd64)...
+✓ ghcr.io/strawberry-code/ragify:1.1.3-tika-arm64
+✓ ghcr.io/strawberry-code/ragify:1.1.3-tika-amd64
+✓ Manifest: ghcr.io/strawberry-code/ragify:1.1.3-tika (multi-arch)
+✓ Manifest: ghcr.io/strawberry-code/ragify:latest-tika (multi-arch)
 
-Prossimo step: /push-ghcr 1.1.0
+Prossimo step: /push-ghcr 1.1.3
 ```
 
 ---
 
 ## Note
 
-- Build usa `--platform linux/amd64` per compatibilità server
-- Il build può richiedere 5-10 minuti
-- Se il build fallisce per rete, riprovare
-- Usa `podman` (o `docker` se non disponibile)
+- Build arm64 è veloce su Mac (nativo)
+- Build amd64 usa emulazione QEMU (~10 min)
+- Le build usano cache per layer non modificati
+- Il manifest combina entrambe le architetture in un singolo tag
+- Docker/Podman seleziona automaticamente l'architettura corretta al pull

.claude/commands/push-ghcr.md

@@ -1,6 +1,6 @@
-# Push Immagini su GitHub Container Registry
+# Push Immagini Multi-Arch su GitHub Container Registry
 
-Pubblica le immagini Docker su ghcr.io/strawberry-code/ragify.
+Pubblica le immagini Docker multi-architettura su ghcr.io/strawberry-code/ragify.
 
 ## Sintassi
 
@@ -31,34 +31,46 @@ podman login ghcr.io -u strawberry-code
 
 **Se NESSUN argomento:** push solo latest
 
-### Step 2: Lista immagini disponibili
+### Step 2: Verifica immagini e manifest
 
 ```bash
+# Lista immagini locali
 podman images | grep ragify
-```
 
-Verifica che le immagini da pushare esistano.
+# Verifica manifest esistenti
+podman manifest inspect ghcr.io/strawberry-code/ragify:{version}-tika 2>/dev/null
+```
 
-### Step 3: Esegui push
+### Step 3: Esegui push dei manifest multi-arch
 
-**Se versione specifica (es. 1.1.0):**
+**Se versione specifica (es. 1.1.3):**
 ```bash
-# Base image
-podman push ghcr.io/strawberry-code/ragify:{version}
-podman push ghcr.io/strawberry-code/ragify:latest
+# Push manifest multi-arch (include arm64 + amd64)
+podman manifest push ghcr.io/strawberry-code/ragify:{version}-tika \
+  docker://ghcr.io/strawberry-code/ragify:{version}-tika
 
-# Tika image
-podman push ghcr.io/strawberry-code/ragify:{version}-tika
-podman push ghcr.io/strawberry-code/ragify:latest-tika
+podman manifest push ghcr.io/strawberry-code/ragify:latest-tika \
+  docker://ghcr.io/strawberry-code/ragify:latest-tika
 ```
 
 **Se solo latest:**
 ```bash
-podman push ghcr.io/strawberry-code/ragify:latest
-podman push ghcr.io/strawberry-code/ragify:latest-tika
+podman manifest push ghcr.io/strawberry-code/ragify:latest-tika \
+  docker://ghcr.io/strawberry-code/ragify:latest-tika
 ```
 
-### Step 4: Verifica tag git
+### Step 4: Verifica su GHCR
+
+```bash
+# Verifica manifest remoto
+podman manifest inspect docker://ghcr.io/strawberry-code/ragify:{version}-tika
+```
+
+Dovresti vedere entrambe le architetture:
+- `linux/amd64`
+- `linux/arm64`
+
+### Step 5: Verifica tag git
 
 Se è stata fatta una release con `/commit patch|minor|major`, verifica che il tag git sia stato pushato:
 
@@ -72,21 +84,22 @@ Se il tag locale esiste ma non è su origin, chiedi se pusharlo:
 git push origin v{version}
 ```
 
-### Step 5: Output
+### Step 6: Output
 
 Mostra:
-- Immagini pubblicate
+- Manifest pubblicati con architetture supportate
 - URL GHCR: `ghcr.io/strawberry-code/ragify`
 - Comando pull: `docker pull ghcr.io/strawberry-code/ragify:latest-tika`
-- Comandi per deploy su server
+- Nota: Docker/Podman seleziona automaticamente l'architettura corretta
 
 ---
 
 ## Troubleshooting
 
 **Errore TLS:**
 ```bash
-podman push --tls-verify=false ghcr.io/strawberry-code/ragify:latest-tika
+podman manifest push --tls-verify=false ghcr.io/strawberry-code/ragify:latest-tika \
+  docker://ghcr.io/strawberry-code/ragify:latest-tika
 ```
 
 **Errore autenticazione:**
@@ -95,22 +108,25 @@ podman login ghcr.io -u strawberry-code
 # Token: ghp_... (con scope write:packages)
 ```
 
+**Manifest non trovato:**
+Prima esegui `/build {version}` per creare le immagini e i manifest.
+
 ---
 
 ## Esempio
 
 ```
-/push-ghcr 1.1.0
+/push-ghcr 1.1.3
 
-Pushing images...
-✓ ghcr.io/strawberry-code/ragify:1.1.0
-✓ ghcr.io/strawberry-code/ragify:latest
-✓ ghcr.io/strawberry-code/ragify:1.1.0-tika
-✓ ghcr.io/strawberry-code/ragify:latest-tika
+Pushing multi-arch manifests...
+✓ ghcr.io/strawberry-code/ragify:1.1.3-tika (linux/amd64, linux/arm64)
+✓ ghcr.io/strawberry-code/ragify:latest-tika (linux/amd64, linux/arm64)
 
-Git tag v1.1.0 pushed to origin.
+Git tag v1.1.3 pushed to origin.
 
-Deploy su server:
+Deploy su server (Ubuntu o Mac):
   docker pull ghcr.io/strawberry-code/ragify:latest-tika
   docker compose down && docker compose up -d
+
+L'architettura corretta viene selezionata automaticamente.
 ```

CHANGELOG.md

@@ -7,8 +7,13 @@ and the project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
+### Added
+- Multi-arch Docker images support (linux/amd64 + linux/arm64) for Ubuntu and Mac compatibility
+- Updated `/build` and `/push-ghcr` slash commands for multi-arch manifest workflow
+
 ### Fixed
-- Dockerfile.tika Tika pre-download script now uses heredoc for proper Python syntax
+- Dockerfile.tika Tika pre-download script now uses heredoc and handles versioned JAR names
+- Removed obsolete mcp_server.py reference from Dockerfiles
 
 ## [1.1.3] - 2025-12-02
 

Dockerfile.tika

@@ -85,24 +85,29 @@ RUN ollama serve & \
 # Pre-download Tika JAR and ensure it's in the expected location
 RUN python3 <<'PYEOF'
 import os
-import shutil
-from tika import parser, tika
+import glob
+from tika import parser
 
-# Trigger download
+# Trigger download (this downloads JAR to /tmp/)
 parser.from_buffer(b'test', xmlContent=False)
 
-# Get the actual JAR path
-jar_path = getattr(tika, 'TikaJarPath', None)
-print(f'Tika JAR downloaded to: {jar_path}')
-
-# Copy to expected location if different
-if jar_path and os.path.exists(jar_path) and jar_path != '/tmp/tika-server.jar':
-    shutil.copy2(jar_path, '/tmp/tika-server.jar')
-    print('Copied to /tmp/tika-server.jar')
-
-# Verify
-assert os.path.exists('/tmp/tika-server.jar'), 'Tika JAR not found at /tmp/tika-server.jar'
-print('Tika JAR verified at /tmp/tika-server.jar')
+# Find the JAR file (handles versioned names like tika-server-standard-3.1.0.jar)
+expected_path = '/tmp/tika-server.jar'
+if os.path.exists(expected_path):
+    print(f'Tika JAR found at {expected_path}')
+else:
+    # Search for versioned JAR
+    jars = glob.glob('/tmp/tika-server*.jar')
+    if jars:
+        print(f'Found JAR: {jars[0]}')
+        os.symlink(jars[0], expected_path)
+        print(f'Created symlink: {expected_path} -> {jars[0]}')
+    else:
+        raise Exception('No Tika JAR found in /tmp/')
+
+# Final verification
+assert os.path.exists(expected_path), f'Tika JAR not found at {expected_path}'
+print(f'Tika JAR verified at {expected_path}')
 PYEOF
 
 # Create data directory for Qdrant