azure-fullstack-deployment

Generates Bicep templates and deployment guidance for Node.js and React apps on Azure.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/samdop/convertonode --skill azure-fullstack-deployment-samdop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-fullstack-deployment
Source: https://github.com/samdop/convertonode/tree/main/.github/skills/azure-fullstack-deployment
Command: npx skills add https://github.com/samdop/convertonode --skill azure-fullstack-deployment-samdop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a migrated ASP.NET MVC to Node.js + React application to Azure involves many decisions across hosting, databases, gateways, identity, and observability. This Skill provides a fixed reference topology, ready-to-use Bicep modules, Dockerfiles, and deployment recipes so teams can provision production infrastructure without designing everything from scratch. ## Core Features & Use Cases - Hosting decision matrix: Choose between Azure Static Web Apps, Container Apps, and App Service for the Vite SPA and Node.js API, with trade-offs documented for each path. - Bicep template set: Subscription-scoped main.bicep with modules for monitoring, Key Vault, PostgreSQL, Azure SQL, Blob Storage, Container Apps, Functions, Static Web Apps, and API Management. - Three deployment paths: All Container Apps, SWA + Container Apps API, or App Service PaaS, each with copy-paste CLI recipes and azd azure.yaml configuration. - Security and observability guidance: Managed identity, Key Vault secret references, APIM JWT validation policies, CSP headers, Application Insights setup, and alert thresholds. - Use Case: After migrating an ASP.NET MVC app to Node.js + React, ask the assistant to generate the Azure deployment assets; it copies the Dockerfile templates, parameterizes main.bicep, and walks you through az deployment sub what-if validation. ## Quick Start Ask the assistant to generate Azure deployment assets for the migrated Node.js API and React web app using the Bicep templates and a production parameter file.

Frequently Asked Questions about azure-fullstack-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Node.js API and React SPA to Azure?

Use the provided Bicep template set with main.bicep at subscription scope. Choose a hosting path: Static Web Apps for the SPA with Container Apps for the API, or all Container Apps, then run az deployment sub create with the example parameters file.

Should I use Azure Container Apps or App Service for a Node.js API?

Container Apps is the recommended default because it offers scale-to-zero, WebSocket support, and shared environment logging. App Service Linux Node is simpler when deployment slots matter more than idle cost savings.

Does Azure API Management work with an OpenAPI document?

Yes. The APIM module imports the OpenAPI document from the API's /api/openapi.json endpoint via the apimOpenApiUrl parameter. APIM then handles JWT validation, CORS, rate limiting, and developer portal exposure.

Can I keep SQL Server instead of migrating to PostgreSQL on Azure?

Yes. Set dbEngine=sqlserver in the parameters to provision Azure SQL Database or Azure SQL Managed Instance instead of PostgreSQL Flexible Server. This applies when Phase 1 of the migration retained SQL Server.

How do I avoid storing secrets in Bicep parameter files?

Pass Key Vault secret URIs such as databaseConnectionStringSecretUri instead of secret values, and use Container Apps Key Vault-backed secrets. Managed identity handles access to Key Vault, Blob Storage, and ACR without credentials.

How do I validate Bicep templates before deploying to Azure?

Run az bicep build on main.bicep to check compilation, then az deployment sub what-if with your parameters file to preview changes. For azd workflows, use azd provision --preview before actual provisioning.