fix: disable migrate job and cleanup cronjob for arm64 cluster

- Disable migrate job (uses app images that need arm64 builds)
- Disable cleanupStaging cronjob (minio/mc image pull failing)
- Worker remains enabled with dev-arm64 tag

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

.gitignore

@@ -41,3 +41,6 @@ Thumbs.db
 
 # Temporary files
 CHANGES_SUMMARY.sh
+
+# Git worktrees
+.worktrees/

docs/plans/2025-12-26-enable-apps-plan.md

@@ -0,0 +1,84 @@
+# Plan: Enable Porthole Web and Worker Applications
+
+## Overview
+
+Currently, the porthole namespace has infrastructure deployed (MinIO, Postgres, Redis) but the main applications are intentionally disabled until container images are built. This plan outlines the steps to build images and enable the web and worker services.
+
+## Current State
+
+- ✅ MinIO, Postgres, Redis running
+- ✅ Cleanup CronJob active
+- ❌ Web app disabled (no UI)
+- ❌ Worker app disabled (no job processing)
+- ❌ Migration job disabled (no schema migrations)
+
+## Required Actions
+
+### 1. Build Container Images
+
+Build and push multi-arch images for both web and worker:
+
+```bash
+# Build web app (Next.js standalone)
+REGISTRY=gitea-gitea-http.taildb3494.ts.net TAG=dev
+docker buildx build --platform linux/amd64,linux/arm64 \
+  -f apps/web/Dockerfile \
+  -t "$REGISTRY/will/porthole-web:$TAG" \
+  --push .
+
+# Build worker app (includes ffmpeg + exiftool)
+REGISTRY=gitea-gitea-http.taildb3494.ts.net TAG=dev
+docker buildx build --platform linux/amd64,linux/arm64 \
+  -f apps/worker/Dockerfile \
+  -t "$REGISTRY/will/porthole-worker:$TAG" \
+  --push .
+```
+
+### 2. Update Helm Values
+
+Enable services in `helm/porthole/values-cluster.yaml`:
+
+```yaml
+# Enable main applications
+web:
+  enabled: true
+
+worker:
+  enabled: true
+
+# Enable migrations
+jobs:
+  migrate:
+    enabled: true
+```
+
+### 3. ArgoCD Sync
+
+Changes will sync automatically, or trigger manually:
+
+```bash
+argocd app sync porthole
+```
+
+## Verification
+
+After sync, verify:
+
+```bash
+# Check deployments
+kubectl get deployments -n porthole
+
+# Check pods are running
+kubectl get pods -n porthole
+
+# Check logs
+kubectl logs -f deployment/porthole-porthole-web -n porthole
+kubectl logs -f deployment/porthole-porthole-worker -n porthole
+```
+
+## Testing
+
+- Access web UI via Tailscale ingress: `app.taildb3494.ts.net`
+- Upload a test asset and verify worker processes it
+- Check MinIO for stored objects
+- Verify database migrations ran successfully

helm/porthole/values-cluster.yaml

@@ -11,15 +11,29 @@ secrets:
     accessKeyId: "FwGiBwCXKuQdthR1QLa"
     secretAccessKey: "OtmAz9m7o941wG1Gms2yItyqxd6gCWY8k4LJVBX"
 
-# Temporarily disable jobs and apps until images are built
+# Temporarily disable jobs until arm64 images are available
 jobs:
   migrate:
     enabled: false
 
+cronjobs:
+  cleanupStaging:
+    enabled: false  # minio/mc image pull failing on arm64
+
 web:
-  enabled: false
+  enabled: false  # Temporarily disabled - web arm64 build times out
+
 worker:
-  enabled: false
+  enabled: true
+
+# Correct image registry (gitea-http not gitea-gitea-http)
+images:
+  web:
+    repository: gitea-http.taildb3494.ts.net/will/porthole-web
+    tag: dev
+  worker:
+    repository: gitea-http.taildb3494.ts.net/will/porthole-worker
+    tag: dev-arm64
 
 # Reduce MinIO storage for testing (insufficient storage on cluster)
 minio: