This project builds heavily on this sample project:

Azure Communication Services Group Calling Hero Sample

It takes the above sample, and makes it work with Azure Static Web Apps. It does this by implementing the back-end part (to get access keys etc) as API calls using Azure Functions, which are now built right into Static Web Apps.

This means that you can have your own group calling scenario up and running by deploying a single web app!

[Create a new Azure Communication Services instance]. Once it's created, go to Keys and make a note of one of the Connection Strings.

Click https://github.com/tomorgan/FamilyCall-ACSSampleAsAzStaticApp/generate

In the Repository name box, enter the name you want for the project

Click Create repository from template.

This step not only creates the Azure Static Web App in your Azure tenant, it also links it to the GitHub repository you just created. That means that the code will automatically be compiled and published for use by the Static Web App (without you needing to do any work!)

1. Navigate to https://portal.azure.com/#create/Microsoft.StaticApp to create a new Static Web App
2. Select your Azure subscription
3. Select or create a new Resource Group
4. Name the app
5. Select a Region closest to you
6. Select the Free SKU
7. Select the Sign-in with GitHub button and authenticate with GitHub

After you sign in with GitHub, enter the repository information.

1. Select your preferred Organization
2. Select the repository you just created from the Repository drop-down
3. Select master from the Branch drop-down

1. In the Build Details section, set the following configuration details:

   1. Select Custom from the Build Presets dropdown
   2. Keep the the default value in the App location box
   3. Make sure thaat the Api location value is set to "api"
   4. Leave the App artifact location box empty

2. Select Review + create.

3. Select Create.

4. Select Go to resource.

The effect of joining your Static Web App to that GitHub repository is that it will kick-off a new build process to compile and deploy the code.

You can see this happening by going back to GitHub, and choose the Actions section of your repository.

Eventually, this action will fail. You can examine the reason why, but it's most probably because of these errors:

These are warnings that I've not been able to workaround in the code, and the only fix I've found is to disable checking for these warnings in the build process.

To fix this, go back to the code in GitHub. At the top, you'll notice that a new folder has been added: .github/workflows. In that folder is a new .yaml file. Edit that file, and insert the following lines immediately after the "name" entry on/around line 16:

env:
  CI: false

The file should now look like this.

Commit the file (to the master branch). This will kick-off the build process again, and this time it should suceed.