Bergfest

Bergfest is a tool to analyze segments on Strava for competetive riding. It uses the Strava API and follows the Strava API Agreement and the Strava Brand Guidelines.

Bergfest is a Azure Static Web App with Blazor as client technology. As starting point the template is used.

Architecture

The following diagram shows the overall architecture:

Solution Structure

• Client: The Blazor WebAssembly application
• Api: The C# Azure Functions API, which the Blazor application will call
• Shared: A C# class library with a shared data model between the Blazor and Functions application
• Bergfest-Webhook: A C# Azure Functions API, essentially with the Webhook to be called by Strava
• BackenLibrary: Repositories (like access to Cosmos DB) to be used by "Api" and "Bergfest-Webhook"

The means to operate Bergfest you need:

• Azure Static Web App - Free Tier is good enough.
• Cosmos DB - Free Tier is good enough.
• Azure Functions - To be checked: Fee tier (consumption based). Otherwise App Service based.
• Storage Account - Event Queue for Strava Webhook and blob storage for image upload.

Deploy to Azure Static Web Apps and Azure Functions

This application can be deployed to Azure Static Web Apps, to learn how, check out our quickstart guide. The following application settings have to be set (in Api and Bergfest-Webhook):

• COSMOS_DB_CONNECTION_STRING: Connection string to access Cosmos DB database
• COSMOS_DB_CONTAINER: Container to be used, e.g. "bergfest"
• COSMOS_DB_DATABASE: Database in Cosmos DB
• STRAVA_ADMIN_ATHLETE_ID: Strava ID of a athlete to be used for administrative tasks as creating segments
• STRAVA_CLIENT_ID: Strava client id for the application
• STRAVA_CLIENT_SECRET: Client secret
• STRAVA_EVENT_QUEUE: Name of event queue, e.g. "stravaeventqueue"
• STRAVA_EVENT_QUEUE_ACCOUNT: Connections string to access event queue

The following application settings are needed in addition to the settings above for the Static Web App.

• BLOB_ACCOUNT: Name of blob storage account to store uploaded images
• BLOB_KEY: Key to access blob account
• BLOB_URI: URI for storage account

The Webhook has to be installed as Azure Functions App. The following application settings are needed for the WebHook Azure Function (in addition to the settings above)

• STRAVA_SUBSCRIPTION_ID: The id received if registering the webhook with Strava. For Strava-Webhooks see: Webhook Events API.