This template will depoy a simple Private DNS Zone
The template will deploy an App service Web App (Windows) in a new or existing App Service Plan (Windows) with MySQL in App enabled.
If you want to deploy in existing App Service Plan instead of a new one, just type the name of your existing App Service Plan and match the SKU
The template will also pull all the necessary Joomla files into the root directory. Note that pulling those files from the source repository might take up to 30 minutes.
Use this article to get you started on using MySQL-in-App feature with your Joomla, if you plan on using the local MySQL for your Joomla installation.
https://github.com/projectkudu/kudu/wiki/MySQL-in-app
ILB App Service Environment v2 Lab - Deploy the basic requirements for an ASEv2 + a VM to test it (will not deploy ASE)
This template will get you ready to deploy an ILB ASE v2 (appserviceenvironment.net) and start practicing/using it. The template will deploy you a VNET and a VM so you can later access the ILB ASE websites. This is good if you want to deploy and configure the ASE yourself and deploy the App Serivce Plan and Web Apps on your own. In details the following will be deployed:
- VNET with a name ILB-ASE-VNET
2 Subnets called "ILB-ASE-SUBNET" with prefix 10.0.0.0.24 and another subnet called "VM-SUBNET" with prefix 10.0.1.0/24 - VM with the size of Standard_B4ms with 127 GB Standard HDD disk
and Windows Server 2019 image - NIC for the VM
- NSG for the VM allowing ports 3389 and 80
- Public static IP for the VM so you can remotely connect ot it
The steps you need to take after this deployment are the following: - Create an ILB App Service Environment v2
- Either create a Private DNS Zone for your ASE domain (asename.appserviceenvironment.net) with a link to the VNET or Install DNS Server on the VM and create a zone there. Set the VNET Dns Servers as custom and to point to the VM's private IP
- Create two A records in that zone. One wildcard (*) pointing to the ILB Address and another wildcard for the scm (in the format of *.scm), again pointing to the ILB Address
- Create an App Service Plan (Isolated) by selecting the ASE as the plan's location
- Create a Web App
This is a premium grade template that will deploy a VNET, VM, Private DNS Zone, ILB App Service Environment V2 (appserviceenvironment.net), App Service Plan (Windows) and a Web App. The template also uses a minimal ammount of customization and the template takes care of the naming for most resrouces. Good for Lab deployments. If you need more customization use the other template.
- VNET with a name ILB-ASE-VNET and Address space of 10.0.0.0/16
- 2 Subnets called "VM-Subnet" with prefix 10.0.1.0/24 and another subnet called "ASE-SUBNET" with prefix 10.0.0.0/24
- VM with the size of Standard_B4ms with 127 GB Standard HDD disk
and Windows Server 2019 image. - NIC for the VM
- NSG for the VM allowing ports 3389
- Public dynamic IP for the VM so you can remotely connect to it
- ILB ASE V2 (appserviceenvironment.net)
- Private DNS Zone covering the asename.appserviceenvironment.net domain
- Virtual network link in the Private DNS Zone to the VNET
- Two A records in that zone. One wildcard (*) pointing to the ILB Address and another wildcard for the scm (in the format of *.scm), again pointing to the ILB Address
- An App Service Plan (Windows) called "ILB-ASE-ASP" in isolated 1 tier (I1) wiht 1 worker
- A Web App called webapp-test
This basically deploys the entire solution with minimal customization. In the end you will have a completely working and configured ILB ASEv2 environment.
This is a diagram of what will be deployed:
This is a premium grade template that will deploy a VNET, VM, Private DNS Zone, ILB App Service Environment V2 (appserviceenvironment.net), App Service Plan (Windows) and a Web app. This represents the entire solution. This version is fully customized which means that it will ask you to name your resouces. Good for production environments.
Here is what is being deployed by the template:
- VNET with Address space of 10.0.0.0/16
- 2 Subnets. 1 that will host the VM with prefix 10.0.1.0/24 and another one with prefix 10.0.0.0/24 that will host the ASE
- Virtual Machine to access the ASE
- NIC for the VM
- NSG for the VM allowing ports 3389
- Public static IP for the VM so you can remotely connect to it
- ILB ASE V2 (appserviceenvironment.net)
- Private DNS Zone covering the asename.appserviceenvironment.net domain
- Virtual network link in the Private DNS Zone to the VNET
- Two A records in that zone. One wildcard (*) pointing to the ILB Address and another wildcard for the scm (in the format of *.scm), again pointing to the ILB Address
- App Service Plan (Windows) in Isolated tier directly deployed into the ASE
- A Web App hosted in this App Service Plan
This basically deploys the entire solution with your own customization. In the end you will have a completely working and configured ILB ASEv2 environment. The only thing that you don't have control over is the address space of the VNET. If you want to change it, feel free to edit it out in the template, just don't forget to change the address space on the A records in the Private DNS Zone too.
This is a diagram of what will be deployed:
This is a premium grade template that will deploy a VNET, ILB ASE, Private DNS Zone with needed records, App Service Plan (Windows) and a Web App. Customizable names for all of these resources. The only thing that's not customizable is the VNET address range. If you want to change it, edit it in the template.
Here is what is being deployed by the template:
- VNET with Address space of 10.0.0.0/16
- 1 Subnet with prefix 10.0.0.0/24 that will host the ASE
- ILB ASE V2 (appserviceenvironment.net)
- Private DNS Zone covering the asename.appserviceenvironment.net domain
- Virtual network link in the Private DNS Zone to the VNET
- Two A records in that zone. One wildcard (*) pointing to the ILB Address and another wildcard for the scm (in the format of *.scm), again pointing to the ILB Address
- App Service Plan (Windows) in Isolated tier directly deployed into the ASE
- A Web App hosted in this App Service Plan
This template is good if you don't need a VM to be deployed. Suitable for production environments.
