DevOps, Environments, and Deployment Strategy

[RocketDelivery2]

TeamBuilder is being designed with professional deployment practices in mind.

The expected backend target is:

• ASP.NET Core Web API
• EF Core Code First
• Azure SQL Server
• GitHub Actions for validation
• Octopus Deploy for future environment-based deployment
• Development, QA, and Production environments

Configuration principles

TeamBuilder should never commit real secrets.

Environment-specific values should be supplied through secure configuration.

Examples include:

• Azure SQL connection strings
• Application Insights connection strings
• API base URLs
• allowed CORS origins
• Octopus variables
• deployment environment names

Expected environments

• Development
• QA
• Production

Platform quality gates

The project should eventually include:

• build validation
• unit test validation
• dependency scanning
• CodeQL scanning
• secret scanning
• pull request checks
• branch protection
• environment approvals for QA and Production

Azure SQL direction

The database direction is:

• EF Core Code First
• SQL Server provider
• Azure SQL Server hosting target
• migrations managed intentionally
• no production secrets in source control
• async queries
• indexes for common search fields
• UTC timestamps
• pagination for large list endpoints

Discussion topics

Use this thread to discuss:

• GitHub Actions workflows
• build validation
• test validation
• CodeQL
• Dependabot
• Azure SQL migrations
• Octopus variable replacement
• environment promotion
• release approvals
• deployment safety
• Application Insights
• health checks
• production readiness

The goal is to keep TeamBuilder easy to run locally and safe to deploy professionally.