MindBlockLabs/mindBlock_Middleware

AI Summary: Create a NestJS health check endpoint (/health) that returns the application status, timestamp, and the status of database and Redis connections (if used). This involves creating a new module and controller, and potentially using the @nestjs/terminus package for structured health checks. The response should be a JSON object with status, timestamp, and a dependencies object indicating connection statuses.

AI Summary: Create a reusable NestJS module for connecting to and managing a Redis client, including error handling, environment variable support, and a service for encapsulating Redis interactions. This module will be used by middleware to implement caching, queueing, or pub/sub functionality.

AI Summary: Develop a NestJS API Gateway middleware module to handle routing, rate limiting (using Redis and RateLimiterFlexible), and secure authentication header forwarding to a backend service (mindBlock_Backend). The gateway should also sanitize responses, log request metadata, support API versioning, and be easily extensible for future microservices.

AI Summary: Develop a NestJS middleware module for centralized authentication. This middleware will intercept requests, validate JWTs or sessions against a specified authentication backend (/auth/verify), attach user data to the request object for downstream services, and handle invalid tokens gracefully. Optional features include Redis caching for session data and configurable options via environment variables.

AI Summary: Integrate a job queue system (BullMQ or Redis Queue) into a NestJS application to handle background tasks asynchronously. This involves installing and configuring the chosen queue library, creating a queue module, defining producers and consumers, connecting to Redis, and implementing job retry, delay, and error handling.

AI Summary: Implement a background worker in a NestJS application using @nestjs/schedule or @nestjs/cron to asynchronously process tasks received via a POST request. The worker should poll for pending tasks, process them (using mocked logic initially), update task status, handle retries, and store results or errors. Enhancements include adding result and error columns to the TaskEntity and creating a reusable processTask utility function.

AI Summary: Implement a NestJS module for managing tasks. This involves creating entities (TaskEntity), services (TaskService), controllers (TaskController), DTOs (CreateTaskDto), and enums (TaskStatusEnum) to handle task creation, storage, status updates (PENDING, PROCESSING, COMPLETED, FAILED), and retrieval. Input validation, error handling, and Swagger documentation are also required.

AI Summary: Implement API key authentication in a NestJS application to protect task ingestion endpoints. This involves creating a custom guard to verify an API key passed in the Authorization header against a value stored in a .env file, returning a 401 Unauthorized response for invalid keys. The guard should be applied globally or to all routes within the TaskController.

AI Summary: Dockerize a NestJS middleware service, creating a Dockerfile and docker-compose.yml to run the application within a containerized environment alongside PostgreSQL (and optionally Redis). This involves configuring environment variables for database connection and defining appropriate ports and dependencies within docker-compose.

AI Summary: Create a REST API endpoint in a NestJS application to receive and store tasks. The endpoint should accept a JSON payload with a task type and payload, validate the input using class-validator, handle database errors, and return the task ID and status. Swagger documentation should also be added.