Installation

Overview

This page lists the installation processes for the Azure Naming Tool.

Choosing An Installation Option

The Azure Naming Tool was designed to be deployed in nearly any environment. This includes as a stand-alone application, or as a container. Each deployment option offers pros/cons, depending on your environment and level of experience.

NOTE:
The Azure Naming Tool requires persistent storage for the configuration files when run as a container. The following processes will explain how to create this volume in your respective environment. All configuration JSON files will be stored in the volume to ensure the configuration is persisted.

• Run as an Azure Web App Using GitHub Action - RECOMMENDED OPTION

  • App Service running a .NET application
  • Ideal for fastest deployment
  • Requires an Azure Web App
  • Utilizes provided GitHub Action for deployment
  • Requires GitHub secrets (instructions in GitHub Action workflow file)
  • Integrated for continuous deployment from GitHub
    
    

• Run as a Docker image

  • Ideal for local deployments
  • Requires a Docker Engine environment
  • Requires a storage volume mount
    
    

• Run as a Docker image with podman

  • Ideal for local deployments
  • Requires a Podman environment
  • Requires a storage volume mount
    
    

• Run as a Web App for Containers

  • App Service running a container
  • Ideal for single container installations
  • Requires an Azure App Service
  • Requires an Azure Files file share for persistent storage
    
    

• Run as an Azure Container App

  • Ideal for multiple container installations (integration with other containers, services, etc.)
  • Requires an Azure Container App
  • Requires an Azure Files file share for persistent storage
    
    

• Run as a Stand-Alone Site

  • Ideal for legacy deployments
  • Requires a web server (IIS, Apache, etc.)
  • Requires building/publshing the .NET Core application