github.com/paybyphone/terraform@v0.9.5-0.20170613192930-9706042ddd51/examples/azure-wordpress-mysql-replication/README.md (about)

     1  # Deploys a WordPress web site backed by MySQL master-slave replication
     2  
     3  This Terraform template was based on [this](https://github.com/Azure/azure-quickstart-templates/tree/master/wordpress-mysql-replication) Azure Quickstart Template. Changes to the ARM template that may have occurred since the creation of this example may not be reflected here.
     4  
     5  This template deploys a WordPress site in Azure backed by MySQL replication with one master and one slave server.  It has the following capabilities:
     6  
     7  - Installs and configures GTID based MySQL replication on CentOS 6
     8  - Deploys a load balancer in front of the 2 MySQL VMs 
     9  - MySQL, SSH, and MySQL probe ports are exposed through the load balancer using Network Security Group rules.  
    10  - WordPress accesses MySQL through the load balancer.
    11  - Configures an http based health probe for each MySQL instance that can be used to monitor MySQL health.
    12  - WordPress deployment starts immediately after MySQL deployment finishes.
    13  - Details about MySQL management, including failover, can be found [here](https://github.com/Azure/azure-quickstart-templates/tree/master/mysql-replication).
    14  
    15  If you would like to leverage an existing VNET, then please see the [documentation here](https://www.terraform.io/docs/import/index.html) to learn about importing existing resources into Terraform and bringing them under state management by this template. To import your existing VNET, you may use this command.
    16  
    17  ```
    18  terraform import azurerm_virtual_network.testNetwork /subscriptions/<YOUR-SUB-ID-HERE>/resourceGroups/<existing-resource-group-name>/providers/Microsoft.Network/virtualNetworks/<existing-vnet-name>
    19  ```
    20  
    21  ## main.tf
    22  The `main.tf` file contains the resources necessary for the MySql replication deployment that will be created. It also contains the Azure Resource Group definition and any defined variables.
    23  
    24  ## website.tf
    25  The `website.tf` contains an `azurerm_template_deployment` that will deploy the Wordpress website.
    26  
    27  ## outputs.tf
    28  This data is outputted when `terraform apply` is called, and can be queried using the `terraform output` command.
    29  
    30  ## provider.tf
    31  You may leave the provider block in the `main.tf`, as it is in this template, or you can create a file called `provider.tf` and add it to your `.gitignore` file.
    32  
    33  Azure requires that an application is added to Azure Active Directory to generate the `client_id`, `client_secret`, and `tenant_id` needed by Terraform (`subscription_id` can be recovered from your Azure account details). Please go [here](https://www.terraform.io/docs/providers/azurerm/) for full instructions on how to create this to populate your `provider.tf` file.
    34  
    35  ## terraform.tfvars
    36  If a `terraform.tfvars` file is present in the current directory, Terraform automatically loads it to populate variables. We don't recommend saving usernames and password to version control, but you can create a local secret variables file and use `-var-file` to load it.
    37  
    38  If you are committing this template to source control, please insure that you add this file to your `.gitignore` file.
    39  
    40  ## variables.tf
    41  The `variables.tf` file contains all of the input parameters that the user can specify when deploying this Terraform template.