Repository files navigation

This guide covers the complete deployment of the TKD Hub application to Azure, including the .NET Azure Functions API, React SPA, and all supporting infrastructure.

• Azure CLI
• Azure Functions Core Tools
• .NET 8.0 SDK
• Node.js 18.x or later
• PowerShell 7+ (for deployment script)
• Git

• Azure subscription with appropriate permissions
• Resource Group (or permissions to create one)

1. Clone and prepare the repository:

   git clone<your-repo-url>cd TKD_Hub_API

2. Login to Azure:

   Connect-AzAccount

3. Run deployment script:

   .\Deploy-TKDHub-Complete.ps1-ResourceGroupName"tkdhub-rg"-AppName"tkdhub"-Location"East US"

4. Follow the prompts and note the generated SQL password

1. Deploy infrastructure:

   az group create --name"tkdhub-rg" --location"East US"az deployment group create \  --resource-group"tkdhub-rg" \  --template-file"./infra/main.bicep" \  --parameters \    appName="tkdhub" \    location="East US" \    sqlAdminLogin="tkdhubadmin" \    sqlAdminPassword="YourSecurePassword123!"

2. Deploy Function App:

   cd src/TKDHubAPI.Functionsdotnet publish --configuration Release --output ./publishfunc azure functionapp publish tkdhub-func --csharp

3. Deploy Static Web App:

   cd frontend/spanpm installnpm run build# Use Static Web Apps CLI or the deployment token from Azureswa deploy ./dist --deployment-token$DEPLOYMENT_TOKEN

1. Create GitHub repository secrets:

   AZURE_CREDENTIALS              # Service principal credentials (JSON)AZURE_SUBSCRIPTION_ID          # Your Azure subscription IDAZURE_RG_NAME                 # Resource group nameAPP_NAME                      # Application nameAZURE_LOCATION                # Azure region (e.g., "East US")SQL_ADMIN_LOGIN              # SQL Server admin usernameSQL_ADMIN_PASSWORD           # SQL Server admin passwordAZURE_STATIC_WEB_APPS_API_TOKEN # Static Web App deployment token

2. Create Azure Service Principal:

   az ad sp create-for-rbac --name"tkdhub-github" \  --role contributor \  --scopes /subscriptions/{subscription-id} \  --sdk-auth

3. Push code to main/master branch to trigger deployment

1. Create Variable Group "TKDHub-Variables":

   azureServiceConnection         # Service connection nameresourceGroupName             # Resource group nameappName                      # Application namelocation                     # Azure regionsqlAdminLogin               # SQL Server admin usernamesqlAdminPassword            # SQL Server admin password (secure)staticWebAppToken           # Static Web App deployment token (secure)

2. Create Azure Service Connection in Azure DevOps

3. Import theazure-pipelines.yml file

• Key Vault Integration: All secrets stored in Azure Key Vault
• Managed Identity: Function App uses System Assigned Managed Identity
• HTTPS Only: All services enforce HTTPS
• CORS Configuration: Proper CORS setup between SPA and API
• SQL Security: Azure SQL with firewall rules

Function App automatically configured with:

• Key Vault references for sensitive settings
• Application Insights integration
• Proper runtime configuration

curl https://{appName}-func.azurewebsites.net/api/health

curl https://{appName}-swa.azurestaticapps.net

Use Azure Data Studio or SQL Server Management Studio to connect:

• Server:{appName}-sql.database.windows.net
• Database:TKDHubDb
• Authentication: SQL Server Authentication

1. Install EF Core tools:

   dotnet tool install --global dotnet-ef

2. Update connection string inappsettings.json or use Azure connection string

3. Run migrations:

   cd src/TKDHubAPI.Infrastructuredotnet ef database update --startup-project ../TKDHubAPI.WebAPI

Execute scripts from thesql.data/ folder in order:

1. Core schema setup
2. Sample data (optional)
3. Permissions and security

1. Function App won't start:

   • Check Application Insights connection string
   • Verify Key Vault access permissions
   • Check function app logs in Azure portal

2. Database connection failures:

   • Verify firewall rules allow Azure services
   • Check connection string format
   • Ensure SQL authentication is enabled

3. Static Web App routing issues:

   • Verifystaticwebapp.config.json is in thepublic folder
   • Check API routes configuration
   • Ensure proper CORS settings

4. Deployment failures:

   • Check Azure subscription limits/quotas
   • Verify resource naming conventions
   • Review deployment logs

• Application Insights: Monitor performance and errors
• Azure Monitor: Resource health and metrics
• Function App Logs: Real-time logging via Azure portal or CLI

• Azure Functions Documentation
• Azure Static Web Apps Documentation
• Azure Bicep Documentation
• Entity Framework Core Documentation

Costs may vary based on usage patterns and region selection.

1. Regular Updates: Keep all packages and dependencies updated
2. Access Reviews: Regularly review Key Vault access policies
3. Monitoring: Set up alerts for unusual activity
4. Backup: Enable point-in-time restore for SQL Database
5. SSL/TLS: Ensure all communications use HTTPS/TLS 1.2+
6. Authentication: Implement proper authentication for API endpoints
7. Secrets Rotation: Regularly rotate passwords and keys