This repo contains the necessary set up to deploy your Shiny app to Azure App Service. You will need the following:
- An
app.Rfile - A
Dockerfile - GitHub Actions workflow file (in this repo, called
container-registry.yaml) - An Azure account, where you are allowed to set up an Azure App Service Plan, and Azure Container Registry
The Docker image will be stored in Azure Container Registry. Azure App Service will run the application from this image.
This project uses renv and will use the renv.lock file to install the necessary R packages in the container.
In the app, you will also see a logout button and a script, called auth.js, that works in combination with Entra ID. You can make use of the built-in authentication and authorization capabilities of Azure App Service to make this happen. See you YouTube tutorials section for more information about adding authentication to Azure App Service.
This is a solution that works, and it's pretty vanilla, but you also have another option: AzureAuth.
There are costs involved with setting up the Azure Container Registry. You pay per day for storage, and you pay per second for build time 💰. With the lowest tier this will result in approximately 5 USD per month, depending on your set region and your build times. Azure App Service has a free tier (F1), which allows 60 CPU-minutes per day and 1GB RAM, and 1GB storage. The first basic App Service tier (B1) starts from 0,018 USD per hour. You can get more information about pricing here.
Microsoft Entra ID is included with Microsoft cloud subscriptions such as Microsoft Azure and Microsoft 365. For more advanced usage, you can move to the paid tiers.
1️⃣ "Deploying Your Shiny Application to Azure App Service" 2️⃣ "Adding Authentication to Azure App Service"
Not looking to have your Shiny app deployed, but an R Plumber API? You can do that in a very similar manner too! Check out this article on how to deploy a Plumber API to Azure App Service, and this follow-up article on how to add authentication to your (Plumber) API.