Deployment Checklist

Use this checklist before every production deployment to ensure nothing is missed.

Do not skip steps. Each item addresses a real failure mode encountered during previous deployments.

Pre-deployment

Environment variables configured

Verify all required environment variables are set in production:

Variable	Service	Required
`SUPABASE_URL`	Backend	Yes
`SUPABASE_SERVICE_ROLE_KEY`	Backend	Yes
`JWT_SECRET`	Backend	Yes
`GROQ_API_KEY`	Backend	Yes
`ASPNETCORE_ENVIRONMENT`	Backend	Recommended
`BACKEND_URL`	Admin Panel	Yes

Never store secrets in code, config files, or Git. Use Azure Application Settings or environment variables.

All variables set and verified

Database schema up to date

Confirm all tables exist in the Supabase public schema:

SELECT table_name FROM information_schema.tables
WHERE table_schema = 'public'
ORDER BY table_name;

Required tables: users, ai_models, threads, thread_messages, comparisons, model_votes, providers, provider_api_keys, system_settings

All 9 tables present

Active models configured

Ensure at least 2 active models exist for arena mode:

SELECT model_name, display_name, provider_name, status
FROM ai_models WHERE status = 'active';

At least 2 active models available

Provider API keys valid

Verify API keys are set and not expired:

SELECT p.provider_name, COUNT(k.id) as key_count
FROM providers p
LEFT JOIN provider_api_keys k ON p.id = k.provider_id AND k.is_active = true
GROUP BY p.provider_name;

Each provider has at least 1 active API key

Backend builds successfully

cd DualMind_Back/src/DualMind.API
dotnet publish -c Release -o ./publish

Build completes with no errors

Tests pass

cd DualMind_Back
dotnet test

All tests green

Deployment

Deploy backend to Azure

CI/CD (Recommended)
Manual

Push to main branch — GitHub Actions handles the rest:

git push origin main

Monitor the deployment in GitHub Actions.

cd DualMind_Back/src/DualMind.API
dotnet publish -c Release -o ./publish
# Deploy ./publish to Azure App Service

Backend deployed successfully

Deploy frontend to Cloudflare Workers

cd DualMind_UI
npx wrangler deploy

Frontend deployed to Cloudflare

Deploy admin panel

cd DualMind_Admin-UI
npm run deploy:prod

Admin panel deployed

Post-deployment verification

Health check passes

curl https://api.dualmindlab.tech/health

Expected: {"status":"healthy"}

API is responding

Authentication works

curl -H "Authorization: Bearer $TOKEN" \
  https://api.dualmindlab.tech/api/arena/models

Returns model list (not 401)

Arena mode functional

Send a test message in arena mode and verify two model responses are returned.

Dual responses received

Streaming works

Test the SSE streaming endpoint:

curl -N "https://api.dualmindlab.tech/api/arena/stream?prompt=test&model=llama-3.3-70b-versatile" \
  -H "Authorization: Bearer $TOKEN"

Tokens stream in real-time

Frontend loads correctly

Visit https://arena.dualmindlab.tech and verify:

Page loads without console errors
Login flow works
Chat interface renders
Dark mode toggles correctly

Frontend fully functional

Admin panel accessible

Admin panel operational

Public sharing works

Share a thread and verify the public URL is accessible without authentication.

Shared threads are publicly viewable

Rollback plan

If any post-deployment check fails, roll back immediately.

Backend Rollback
Frontend Rollback

Redeploy the previous version from Azure App Service → Deployment Center → select previous deployment.Or revert the Git commit:

git revert HEAD
git push origin main

npx wrangler rollback

Always keep the previous deployment artifacts available for at least 48 hours after a new deployment.

Getting Started

Core Concepts

Architecture

Database

Frontend Guide

Development

Deployment

Production Deployment Checklist

Deployment Checklist

Pre-deployment

Deployment

Post-deployment verification

Rollback plan

​Deployment Checklist

​Pre-deployment

​Deployment

​Post-deployment verification

​Rollback plan

Deployment Checklist

Pre-deployment

Deployment

Post-deployment verification

Rollback plan