*Note: $CI_PROJECT_DIR is the full path the repository is cloned to, and where the job runs from.
If you are not using sample app, the values for APP_PATH, API_PATH and OUTPUT_PATH need to change to match the values in your application.
Location of your application code.
Enter $CI_PROJECT_DIR/ if your application source code is at the root of the repository, or $CI_PROJECT_DIR /app if your application code is in a directory called app.
Location of your Azure Functions code.
Enter $CI_PROJECT_DIR /api if your app code is in a folder called api.
Location of the build output directory relative to the APP_PATH.
If your application source code is located at $CI_PROJECT_DIR /app, and the build script outputs files to the $CI_PROJECT_DIR /app/build folder, then set $CI_PROJECT_DIR /app/build as the OUTPUT_PATH value.
API token for deployment
Include API_TOKEN: $DEPLOYMENT_TOKEN
Once the deployment is successful, navigate to the Azure Static Web Apps Overview which includes links to the deployment configuration. Note how the Source link now points to the GitLab.
Select the URL to see your newly deployed website.
URL for newly deployed app
Clean up resources
Clean up the resources you deployed by deleting the resource group.
From the Azure portal, select Resource group from the left menu.
Enter the resource group name in the Filter by name field.
Select the resource group name you used in this tutorial.