Skip to main content

Deployment Guide

Document Status: Placeholder - To be completed in Phase 4

Overview

LC DocCheck is deployed to Azure using Infrastructure as Code (Bicep) and GitHub Actions for CI/CD.

Environments

EnvironmentPurposeURL
DevelopmentFeature development and testingInternal
StagingPre-production validationInternal
ProductionLive system for RudolfProtected

Azure Resources

Resource Group: rg-doccheck-prod

ResourceTypeSKU
Cosmos DBServerlessServerless
Function AppConsumptionY1
Storage AccountStandardLRS
AI FoundryStandardS0
Static Web AppFreeFree

Deployment Process

1. Infrastructure (First Time Only)

# Deploy Bicep templates
az deployment group create \
--resource-group rg-doccheck-prod \
--template-file infra/main.bicep \
--parameters environment=prod

2. Azure Functions

# From projects/doc-check/functions/
func azure functionapp publish doccheck-functions-prod

3. UI (Power Apps Code App)

The UI is packaged and deployed via Power Platform CLI:

# Build the React app
npm run build

# Package for Power Apps
pac pcf push --publisher-prefix lcdc

Configuration

Environment Variables (Function App)

VariableDescription
COSMOS_CONNECTIONCosmos DB connection string
STORAGE_CONNECTIONBlob storage connection string
AI_FOUNDRY_ENDPOINTAzure AI Foundry endpoint
AI_FOUNDRY_KEYAzure AI Foundry key

Application Settings

Settings are managed via Azure Portal or Bicep parameters. Never commit secrets to source control.

Monitoring

  • Azure Application Insights for telemetry
  • Log Analytics workspace for aggregated logs
  • Alerts configured for:
    • Function failures > 5/min
    • Response time > 5s
    • Cosmos RU consumption > 80%

Rollback Procedure

  1. Identify last known good deployment
  2. Re-deploy from that commit/tag
  3. Verify functionality
  4. Investigate root cause

See Also