Platform target

Azure Static Web Apps

Azure can deploy Nift's normal public/ output. The target adds Azure's application configuration as a tracked raw file so it is reproduced at the root of every Nift build.

nift init --target=azure

What Nift creates

content/staticwebapp.config.json
        │ tracked as raw JSON
        ▼
public/staticwebapp.config.json

Edit the file under content/, not the generated copy under public/. Microsoft requires staticwebapp.config.json to reach the root of the build output when a build step is used.

Routing and security

Azure's configuration file can define route rules, redirects/rewrites, authorization by role, fallback behaviour, response overrides, headers, MIME types and networking settings. Azure Static Web Apps also has built-in authentication concepts and can expose user information to the frontend/API.

Adding an API

An Azure Functions project commonly lives in an api/ directory beside the static frontend. Your deployment workflow can point Azure Static Web Apps at both the Nift output and the Functions source/build output.

Build configuration

Azure's deployment workflow distinguishes application location, optional API location and output location. Configure the workflow to run Nift (with Nift installed in that build environment) and deploy public/.

Official references: application configuration, build configuration, authentication/authorization, and Functions API integration.