If you want to get Azure Static Web Apps running and you’ve been suffering interminable Azure subscription and other mysterious issues, then you’re at the right place.
You want to have installed the following things.
- Azure command line tools [link]
- Static Web App command line tools [link]
- Node Package Manager [link]
- Node Version Manager (or a similar tool) to run Node 16 [link]
There’s some Azure stuff you need to have ready, too.
- Get an Azure account
- Get your tenant-id and subscription-id from within Azure Portal
- Be sure to enable
Microsoft.Webon your subscription from “Resource Providers”
Lastly you need some code to get started.
- Clone this repo
- Move it to your own computer with git magic like
gh repo clone johnmaeda/reponame
- Okay. You’re good to go!
cdto the local directory and let’s get started!
- Be sure to be logged out of Azure so any existing identity has been cleared out.
- Login to Azure.
% az login
- Use Node version 16 if you don’t have it. Be sure to set your session to use 16.
% nvm install 16(this will set the session you’re in to 16)
% nvm ls(this will list the available versions)
% nvm use 16.20.2(this will switch you to 16.20.2 if it’s in your list)
- Install react-scripts.
% npm install react-scripts(static web apps CLI requires version 16)
- Invoke the swa with your tenant-id. You may not need your tenant-id, but I did.
% swa login --tenant-id longalphanumericstring --verbose=silly
- Get going with the defaults for swa.
% swa(go with all the defaults — they’re very good)
% swa start
% swa build
- Get it up on the Internet.
% swa deploy --verbose=silly