How to: Deploy Fluid applications using Azure Static Web Apps

This article demonstrates how to deploy Fluid apps using Azure Static Web Apps. The FluidHelloWorld repository contains a Fluid application called DiceRoller that enables all connected clients to roll a dice and view the result. In this how-to, you deploy the DiceRoller application to Azure Static Web Apps using the Visual Studio Code extension.

If you don't have an Azure subscription, create a free trial account.

Prerequisites

Fork and clone the repository

Navigate to https://github.com/microsoft/FluidHelloWorld and click the Fork button to create your own fork of the FluidHelloWorld repo.

Then clone your fork to your local machine using the following command.

git clone -b main-azure https://github.com/<YOUR_GITHUB_ACCOUNT_NAME>/FluidHelloWorld.git

Make sure to replace <YOUR_GITHUB_ACCOUNT_NAME> with your GitHub username.

Next, open Visual Studio Code and go to File > Open Folder to open the cloned repository in the editor.

Connect to Azure Fluid Relay Service

You can connect to Azure Fluid Relay service by providing the tenant ID and key that is uniquely generated for you when creating the Azure resource. You can build your own token provider implementation or you can use the two token provider implementations that the Fluid Framework provides: InsecureTokenProvider and AzureFunctionTokenProvider.

To learn more about using InsecureTokenProvider for local development, see Connecting to the service and Authentication and authorization in your app.

Using AzureFunctionTokenProvider

AzureFunctionTokenProvider is a token provider that does not expose the secret key in client-side code and can be used in production scenarios. This token provider implementation can be used to fetch a token from an HTTPS endpoint that is responsible for signing access tokens with the tenant key. This provides a secure way to generate the token and pass it back to the client app.

import { AzureClient, AzureFunctionTokenProvider } from "@fluidframework/azure-client";

const config = {
    tenantId: "myTenantId",
    tokenProvider: new AzureFunctionTokenProvider("https://myAzureAppUrl"+"/api/GetAzureToken", { userId: "test-user",userName: "Test User" }),
    orderer: "https://myOrdererUrl",
    storage: "https://myStorageUrl",
};

const clientProps = {
    connection: config,
};

const client = new AzureClient(clientProps);

In order to use this token provider, you need to deploy an HTTPS endpoint that will sign tokens, and pass the URL to your endpoint to the AzureFunctionTokenProvider.

Deploying an Azure Function using Azure Static Web apps

Azure Static Web Apps allow you to develop a full-stack web site without needing to deal with the server-side configuration of an entire web hosting environment. You can deploy Azure Functions alongside your static website. Using this capability, you can deploy an HTTP-triggered Azure Function that will sign tokens.

For more information about deploying Azure Function-powered APIs to your static web app see Add an API to Azure Static Web Apps with Azure Functions.

Note

You can use the example Azure Function code in Implementing an Azure Function to sign tokens to implement your function.

Once your Azure Function is deployed, you must update the URL passed to the AzureFunctionTokenProvider.

import { AzureClient } from "@fluidframework/azure-client";

const config = {
    tenantId: "myTenantId",
    tokenProvider: new AzureFunctionTokenProvider("https://myStaticWebAppUrl/api/GetAzureToken", { userId: "test-user",userName: "Test User" }),
    orderer: "https://myOrdererUrl",
    storage: "https://myStorageUrl",
};

const clientProps = {
    connection: config,
};

const client = new AzureClient(config);

Run the npm run build command from the root directory to rebuild the app. This will generate a dist folder with the application code that should be deployed to the Static Web app.

Sign in to Azure

If you already use the Azure service extensions, you should already be logged in and can skip this step.

Once you've installed an extension in Visual Studio Code, you need to sign into your Azure account.

  1. In Visual Studio Code, select the Azure explorer icon, then select Sign in to Azure, and follow the prompts.

    Sign in to Azure through VS Code

  2. After signing in, verify that the email address of your Azure account appears in the Status Bar and your subscription(s) appears in the Azure explorer:

    VS Code Azure explorer showing subscriptions

Create a static web app

  1. Inside Visual Studio Code, select the Azure logo in the Activity Bar to open the Azure extensions window.

    An image of the Azure Logo on a white background.

    Note

    You must sign in to Azure and GitHub in Visual Studio Code to continue. If you are not already authenticated, the extension will prompt you to sign in to both services during the creation process.

  2. Under the Static Web Apps label, select the plus sign.

    An image of the Static Web Apps extension UI, highlighting the create button.

    Note

    The Azure Static Web Apps Visual Studio Code extension streamlines the creating process by using a series of default values. If you want to have fine-grained control of the creation process, open the command palate and select Azure Static Web Apps: Create Static Web App... (Advanced).

  3. The command palette opens at the top of the editor and prompts you to select a subscription name.

    Select your subscription and press Enter.

    An image of the Azure subscription selection UI, which shows a single subscription to be selected.

  4. Next, name your application.

    Type my-first-static-web-app and press Enter.

    An image of the Static Web Apps extension UI, which shows a text box to enter the name of the application.

  5. Select a region close to you.

    Note

    Azure Static Web Apps globally distributes your static assets. The region you select determines where your optional staging environments and API function app will be located.

  6. Set other deployment options.

    • When asked to select a build preset to configure default project structure, select Custom.
    • Location of application code: /
    • Location of Azure Function code: api
  7. Once the app is created, a confirmation notification is shown in Visual Studio Code.

    An image of the notification shown in Visual Studio Code when the app is created. The notification reads: Successfully created new static web app my-first-static-web-app. GitHub Actions is building and deploying your app, it will be available once the deployment completes.

    As the deployment is in progress, the Visual Studio Code extension reports the build status to you.

    An image of the Static Web Apps extension UI, which shows a list of static web apps under each subscription. The highlighted static web app has a status of Waiting for Deployment displayed next to it.

    Once the deployment is complete, you can navigate directly to your website.

  8. To view the website in the browser, right-click on the project in the Static Web Apps extension, and select Browse Site.

    An image of the menu that is shown when right-clicking on a static web app. The Browse Site option is highlighted.

  9. The location of your application code, Azure Function, and build output is part of the azure-static-web-apps-xxx-xxx-xxx.yml workflow file located in the /.github/workflows directory. This file is automatically created when create the Static Web app. It defines a GitHub Action to build and deploy your Static Web app.

Clean up resources

If you're not going to continue to use this application, you can delete the Azure Static Web Apps instance through the extension.

In the Visual Studio Code Explorer window, return to the Static Web Apps section and right-click on my-first-static-web-app and select Delete.

An image of the menu that is shown when right-clicking on a static web app. The Delete option is highlighted.