feat(infra): switch Redis to Valkey + add RedisInsight cache browser

Valkey 8 (BSD-3, the Linux Foundation Redis fork) replaces the
source-available Redis image across Aspire and both compose files. Drop-in:
the kit uses only StackExchange.Redis over RESP (cache, data protection,
SignalR backplane, quota) with no Redis Stack modules, and Hangfire is on
Postgres. Resource/service name stays "redis" so connection strings and
config keys do not churn.

- AppHost: AddRedis(...).WithImage("valkey/valkey","8") + .WithRedisInsight()
  (auto-wired cache browser; SSPL but dev-only). The valkey image ships
  redis-* symlinks and supports Aspire's TLS command, so the Redis
  integration works unmodified.
- docker-compose.yml (dev): valkey/valkey:8-alpine.
- deploy/docker (prod): valkey/valkey:8-alpine + valkey-server/valkey-cli.

Verified by booting Aspire: Valkey starts clean (tcp+tls listeners),
authenticated PING returns PONG, RedisInsight comes up auto-connected.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: iammukeshm

deploy/docker/docker-compose.yml

@@ -31,19 +31,19 @@ services:
     #   - "5432:5432"
 
   redis:
-    image: redis:7-alpine
+    image: valkey/valkey:8-alpine
     container_name: fsh-redis
     restart: unless-stopped
     command:
-      - redis-server
+      - valkey-server
       - --requirepass
       - ${REDIS_PASSWORD:?REDIS_PASSWORD is required}
       - --appendonly
       - "yes"
     volumes:
       - redis_data:/data
     healthcheck:
-      test: ["CMD-SHELL", "redis-cli -a $$REDIS_PASSWORD PING | grep PONG"]
+      test: ["CMD-SHELL", "valkey-cli -a $$REDIS_PASSWORD PING | grep PONG"]
       interval: 5s
       timeout: 3s
       retries: 12

docker-compose.yml

@@ -15,7 +15,7 @@ services:
       - postgres-data:/var/lib/postgresql/data
 
   redis:
-    image: redis:7-alpine
+    image: valkey/valkey:8-alpine
     ports:
       - "6379:6379"
 

src/Host/FSH.Starter.AppHost/AppHost.cs

@@ -18,9 +18,20 @@
 
 var postgres = postgresServer.AddDatabase("fsh-db");
 
+// Valkey (BSD-3, the Linux Foundation's Redis fork) via Aspire's Redis
+// integration. Drop-in over RESP: the kit uses only StackExchange.Redis
+// (cache, data protection, SignalR backplane, quota) with no Redis Stack
+// modules, and Hangfire is on Postgres — so nothing is Redis-specific.
+// Resource name stays "redis" so connection strings / config keys don't churn.
 var redis = builder.AddRedis("redis")
+    .WithImage("valkey/valkey", "8")
     .WithDataVolume("fsh-redis-data")
-    .WithLifetime(ContainerLifetime.Persistent);
+    .WithLifetime(ContainerLifetime.Persistent)
+    // RedisInsight cache browser — Aspire auto-wires it to the resource above,
+    // so it connects to Valkey with no manual config. It's SSPL (source-available),
+    // but as a dev-only tool that's never redistributed the licensing impact is nil.
+    // Prefer a strictly-MIT toolchain? Swap to .WithRedisCommander().
+    .WithRedisInsight();
 
 // Build a plain TCP (non-TLS) Redis connection string using the secondary endpoint.
 // Aspire 13.x enables TLS on the primary Redis port by default; the secondary endpoint is plain TCP.