My own Azure resume.
- Frontend folder contains the website.
- main.js contains visitor counter code.
const functionApi = ''; - Responsible for collecting API from Azure Functions JSON.
- GitHub account
- Azure account
- Azure CLI
- .NET Core 3.1 LTS
- Azure Functions Core Tools
- Visual Studio Code
- Visual Code Extensions
- Azure Functions Extensions
- C# Extension
- Azure Storage Extension
The front-end is a static site with HTML, CSS, and JavaScript. It's static and has a visitor counter. The visitor counter data fetched via an API call to an Azure Function.
- I used this template to create my site.
- I'm no JavaScript dev, but this article explains well and in a simple way how to use it to make an API call.
- Azure storage explorer is a handy tool to use when working with Storage Accounts
- This helped me to deploy static site to blob storage.
The back-end is an HTTP triggered Azure Functions with Cosmos DB input and output binding. The Function is triggered, it retrieves the CosmosDB item, adds 1 to it, and saves it and returns its value to the caller.
- Create a Cosmos DB account via command line or from the portal.
- Create an HTTP triggered Azure Function in Visual Studio Code.
- Azure Functions Cosmos DB bindings
- Retrieve a Cosmos DB item with Functions binding.
- Write to a Cosmos DB item with Functions binding.
- Important note: enable CORS with Azure Functions locally and once it's deployed to Azure for you website to be able to call it.
Testing is important, though my tests are simple, they exist. I am using .NET but some of these resources will apply to any language.
- This is how you can deploy a blob storage static site with GitHub actions.
- This is how you can deploy an Azure Function to Azure with GitHub Actions.
- Implement .NET testing in GitHub Actions.