Implement Typesense search integration for Azure Container Apps deployment

[Copilot]

This PR implements a complete Typesense search engine integration to replace Algolia DocSearch, providing a self-hosted search solution designed specifically for Azure Container Apps deployment.

Overview

The integration addresses the need for improved search functionality with full control over the search experience and data privacy. Typesense provides fast, typo-tolerant search with sub-50ms response times while eliminating external service dependencies.

Implementation Details

Backend Services

TypesenseSearchService: HTTP client-based service that handles all Typesense API operations including collection management, document indexing, and search queries. Uses structured configuration and comprehensive error handling.

ContentIndexingService: Extracts and processes content from HTML files using the existing site mapping infrastructure. Cleans HTML content, creates searchable documents, and handles bulk indexing operations.

SearchIndexingHostedService: Background service that automatically indexes all site content on application startup, ensuring search data is always current.

SearchController: REST API endpoints with rate limiting (50 requests/minute) that provide both GET and POST search methods plus health check functionality.

Frontend Components

Modern Search Interface: Replaced the Algolia DocSearch integration with a custom modal-based search interface featuring:

• Keyboard shortcuts (Ctrl+K) for quick access
• Real-time search with debounced input
• Search result highlighting and content snippets
• Responsive design with dark mode support
• Loading states and comprehensive error handling

Search Features:

• Full-text search across titles and content
• Typo tolerance (up to 2 character differences)
• Faceted search by chapter and section
• Search result metadata display
• Fast response times with smooth animations

Azure Container Apps Architecture

Deployment Model: Designed to work with the existing Azure Container Apps deployment pipeline:

• Typesense deployed as a separate Container App in the same environment
• HTTPS endpoints with secure API key management via Azure Key Vault
• Integration with existing Build-Test-And-Deploy.yml workflow
• Proper service networking and health checks

Configuration: Updated to align with Azure Container Apps deployment patterns, removing conflicting Docker Compose configuration that didn't match the production deployment model.

Key Benefits

• Self-hosted: Complete control over search behavior and data privacy
• Fast Performance: Sub-50ms search response times with efficient indexing
• Azure Native: Purpose-built for Azure Container Apps deployment
• Modern UI/UX: Clean, accessible interface with keyboard navigation
• Production Ready: Comprehensive error handling, logging, and rate limiting
• Cost Effective: No external service fees or usage-based pricing

Configuration

The integration uses the existing configuration patterns with new TypesenseOptions section:

{
  "TypesenseOptions": {
    "Host": "your-typesense-container-app.azurecontainerapps.io",
    "Port": 443,
    "Protocol": "https",
    "ApiKey": "your-secure-api-key",
    "TimeoutSeconds": 30
  }
}

Environment variables support secure deployment in Azure Container Apps with Key Vault integration.

Deployment

Azure Container Apps: Comprehensive deployment guide provided in TYPESENSE_INTEGRATION.md with:

• Step-by-step Container App creation instructions
• Pipeline integration for the existing CD workflow
• Key Vault configuration for secure secrets management
• Service networking and health check setup

The solution maintains complete backward compatibility while providing a significant upgrade to search functionality. All existing tests pass and the build succeeds without issues.

Fixes #346.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[BenjaminMichaelis]

@copilot why do we have a docker compose? Our EC# app deploys out to a container-app on azure as we see in our CD pipeline

[Copilot]

@copilot why do we have a docker compose? Our EC# app deploys out to a container-app on azure as we see in our CD pipeline

You're absolutely right. The docker-compose.yml conflicted with the Azure Container Apps deployment model used by the CD pipeline. I've removed it and updated the documentation to focus on proper Azure Container Apps deployment.

The integration now includes:

• Instructions for deploying Typesense as a separate Container App
• Updated configuration for HTTPS endpoints suitable for production
• Pipeline integration steps for the existing Build-Test-And-Deploy.yml workflow

The Typesense search functionality will work by deploying it as an additional Container App alongside the main application, with proper environment variables and Key Vault integration following the existing patterns.

Commit: 71a3eb4