Configurar MCP en mismo dominio de la app principal
All checks were successful
build-and-deploy / build (push) Successful in 10s
build-and-deploy / deploy (push) Successful in 3s

- Cambiar router MCP para usar APP_DOMAIN/mcp en lugar de dominio separado
- Prioridad 200 para que tenga precedencia sobre otros routers
- Eliminar variable MCP_DOMAIN del workflow y .env.example
- Actualizar README con nueva configuración de endpoints
- El servidor MCP estará en docs.nucleoriofrio.com/mcp sin Authentik
This commit is contained in:
2025-10-13 19:39:32 -06:00
parent 7234bb63bf
commit 7ee9e69b28
4 changed files with 12 additions and 11 deletions

View File

@@ -68,10 +68,11 @@ services:
# Service
- "traefik.http.services.${APP_NAME}-mcp.loadbalancer.server.port=3000"
# Router sin autenticación con PathPrefix para /mcp
- "traefik.http.routers.${APP_NAME}-mcp.rule=Host(`${MCP_DOMAIN}`) && PathPrefix(`/mcp`)"
# Router sin autenticación para /mcp - Mayor prioridad que la app principal
- "traefik.http.routers.${APP_NAME}-mcp.rule=Host(`${APP_DOMAIN}`) && PathPrefix(`/mcp`)"
- "traefik.http.routers.${APP_NAME}-mcp.entrypoints=websecure"
- "traefik.http.routers.${APP_NAME}-mcp.tls.certresolver=letsencrypt"
- "traefik.http.routers.${APP_NAME}-mcp.priority=200"
- "traefik.http.routers.${APP_NAME}-mcp.service=${APP_NAME}-mcp"
# Headers personalizados para MCP