From c99d4f2e6ae39135ccd624f5b7ddb85c81c58c92 Mon Sep 17 00:00:00 2001 From: Michael Cade Date: Fri, 18 Nov 2022 15:00:44 +0000 Subject: [PATCH] change file locations 2022 --- 2022/Days/day46.md | 2 +- 2022/Days/day60.md | 2 +- 2022/Days/day61.md | 2 +- 2022/Days/day65.md | 2 +- es/Days/day46.md | 2 +- es/Days/day60.md | 2 +- es/Days/day61.md | 2 +- es/Days/day65.md | 2 +- ja/Days/day46.md | 2 +- ja/Days/day54.md | 2 +- ja/Days/day60.md | 2 +- ja/Days/day61.md | 2 +- ja/Days/day65.md | 2 +- pl/day46.md | 2 +- pl/day60.md | 2 +- pl/day61.md | 2 +- pl/day65.md | 2 +- zh_cn/Days/day46.md | 2 +- zh_cn/Days/day54.md | 2 +- zh_cn/Days/day60.md | 2 +- zh_cn/Days/day61.md | 2 +- zh_cn/Days/day65.md | 2 +- zh_tw/Days/day46.md | 2 +- zh_tw/Days/day54.md | 2 +- zh_tw/Days/day60.md | 2 +- zh_tw/Days/day61.md | 2 +- zh_tw/Days/day65.md | 2 +- 27 files changed, 27 insertions(+), 27 deletions(-) diff --git a/2022/Days/day46.md b/2022/Days/day46.md index bc281e8..2239829 100644 --- a/2022/Days/day46.md +++ b/2022/Days/day46.md @@ -156,7 +156,7 @@ This is also a great resource for samples of docker-compose applications with mu In the above repository, there is a great example which will deploy an Elasticsearch, Logstash, and Kibana (ELK) in single-node. -I have uploaded the files to the [Containers folder](/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` +I have uploaded the files to the [Containers folder](2022/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` ![](Images/Day46_Containers15.png) diff --git a/2022/Days/day60.md b/2022/Days/day60.md index a080daa..a7b7e65 100644 --- a/2022/Days/day60.md +++ b/2022/Days/day60.md @@ -59,7 +59,7 @@ You can find out more information on the [Docker Provider](https://registry.terr The above is a very simple demo of what can be done with Terraform plus Docker and how we can now manage this under the Terraform state. We covered docker-compose in the containers section and there is a little crossover in a way between this, infrastructure as code as well as then Kubernetes. -To show this and how Terraform can handle a little more complexity, we are going to take the docker-compose file for WordPress and MySQL that we created with docker-compose and we will put this to Terraform. You can find the [docker-wordpress.tf](/Days/IaC/Docker-WordPress/docker-WordPress.tf) +To show this and how Terraform can handle a little more complexity, we are going to take the docker-compose file for WordPress and MySQL that we created with docker-compose and we will put this to Terraform. You can find the [docker-wordpress.tf](2022/Days/IaC/Docker-WordPress/docker-WordPress.tf) ``` terraform { diff --git a/2022/Days/day61.md b/2022/Days/day61.md index 6d54c64..084b8b7 100644 --- a/2022/Days/day61.md +++ b/2022/Days/day61.md @@ -24,7 +24,7 @@ Now we could use `kubectl` as we have shown in previous sections. But there are ### Simple Kubernetes Demo -Much like the demo we created in the last session, we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](/Days/IaC/Kubernetes/Kubernetes.tf) +Much like the demo we created in the last session, we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](2022/Days/IaC/Kubernetes/Kubernetes.tf) In that file we are going to define our Kubernetes provider, we are going to point to our kubeconfig file, create a namespace called nginx, and then we will create a deployment which contains 2 replicas and finally service. diff --git a/2022/Days/day65.md b/2022/Days/day65.md index 23b2f6b..cec5a7a 100644 --- a/2022/Days/day65.md +++ b/2022/Days/day65.md @@ -59,7 +59,7 @@ tasks: We are going to use Vagrant to set up our node environment, I am going to keep this at a reasonable 4 nodes but you can hopefully see that this could easily be 300 or 3000 and this is the power of Ansible and other configuration management tools to be able to configure your servers. -You can find this file located here ([Vagrantfile](/Days/Configmgmt/Vagrantfile)) +You can find this file located here ([Vagrantfile](2022/Days/Configmgmt/Vagrantfile)) ```Vagrant Vagrant.configure("2") do |config| diff --git a/es/Days/day46.md b/es/Days/day46.md index 0a6d44f..983c023 100644 --- a/es/Days/day46.md +++ b/es/Days/day46.md @@ -146,7 +146,7 @@ This is also a great resource for samples of docker-compose applications with mu In the above repository, there is a great example which will deploy an Elasticsearch, Logstash, and Kibana (ELK) in single-node. -I have uploaded the files to the [Containers folder](/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` +I have uploaded the files to the [Containers folder](2022/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` ![](Images/Day46_Containers15.png) diff --git a/es/Days/day60.md b/es/Days/day60.md index a9b8da5..f4873ce 100644 --- a/es/Days/day60.md +++ b/es/Days/day60.md @@ -49,7 +49,7 @@ You can find out more information on the [Docker Provider](https://registry.terr The above is a very simple demo of what can be done with Terraform plus Docker and how we can now manage this under the Terraform state. We covered docker-compose in the containers section and there is a little crossover in a way between this, infrastructure as code as well as then Kubernetes. -To show this and how Terraform can handle a little more complexity, we are going to take the docker-compose file for WordPress and MySQL that we created with docker-compose and we will put this to Terraform. You can find the [docker-wordpress.tf](/Days/IaC/Docker-WordPress/docker-WordPress.tf) +To show this and how Terraform can handle a little more complexity, we are going to take the docker-compose file for WordPress and MySQL that we created with docker-compose and we will put this to Terraform. You can find the [docker-wordpress.tf](2022/Days/IaC/Docker-WordPress/docker-WordPress.tf) ``` terraform { diff --git a/es/Days/day61.md b/es/Days/day61.md index a9727e8..4c80144 100644 --- a/es/Days/day61.md +++ b/es/Days/day61.md @@ -14,7 +14,7 @@ Now we could use `kubectl` as we have shown in previous sections. But there are ### Simple Kubernetes Demo -Much like the demo we created in the last session, we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](/Days/IaC/Kubernetes/Kubernetes.tf) +Much like the demo we created in the last session, we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](2022/Days/IaC/Kubernetes/Kubernetes.tf) In that file we are going to define our Kubernetes provider, we are going to point to our kubeconfig file, create a namespace called nginx, and then we will create a deployment which contains 2 replicas and finally service. diff --git a/es/Days/day65.md b/es/Days/day65.md index d3f57db..a13cdf9 100644 --- a/es/Days/day65.md +++ b/es/Days/day65.md @@ -49,7 +49,7 @@ tasks: We are going to use Vagrant to set up our node environment, I am going to keep this at a reasonable 4 nodes but you can hopefully see that this could easily be 300 or 3000 and this is the power of Ansible and other configuration management tools to be able to configure your servers. -You can find this file located here ([Vagrantfile](/Days/Configmgmt/Vagrantfile)) +You can find this file located here ([Vagrantfile](2022/Days/Configmgmt/Vagrantfile)) ```Vagrant Vagrant.configure("2") do |config| diff --git a/ja/Days/day46.md b/ja/Days/day46.md index 00b5b5c..f21e9bb 100644 --- a/ja/Days/day46.md +++ b/ja/Days/day46.md @@ -154,7 +154,7 @@ This is also a great resource for samples of docker compose applications with mu In the above repository there is a great example which will deploy an Elasticsearch, Logstash, and Kibana (ELK) in single-node. -I have uploaded the files to the [Containers folder](/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` +I have uploaded the files to the [Containers folder](2022/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` ![](Images/Day46_Containers15.png) diff --git a/ja/Days/day54.md b/ja/Days/day54.md index 10b78ae..563826e 100644 --- a/ja/Days/day54.md +++ b/ja/Days/day54.md @@ -29,7 +29,7 @@ In this first step we are simply going to create a stateless application within In the first demo we want to define everything we do with YAML, we could have a whole section on YAML but I am going to skim over this and leave some resources at the end that will cover YAML in more detail. -We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](Days\Kubernetes\nginx-stateless-demo.yaml) +We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](2022\Days\Kubernetes\nginx-stateless-demo.yaml) ``` apiVersion: v1 diff --git a/ja/Days/day60.md b/ja/Days/day60.md index 61b4dbf..374a83b 100644 --- a/ja/Days/day60.md +++ b/ja/Days/day60.md @@ -58,7 +58,7 @@ You can find out more information on the [Docker Provider](https://registry.terr The above is a very simple demo of what can be done with Terraform plus Docker and how we can now manage this under the Terraform state. We covered docker compose in the containers section and there is a little crossover in a way between this, infrastructure as code as well as then Kubernetes. -For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](/Days/IaC/Docker-Wordpress/docker-wordpress.tf) +For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](2022/Days/IaC/Docker-Wordpress/docker-wordpress.tf) ``` terraform { diff --git a/ja/Days/day61.md b/ja/Days/day61.md index c3c819b..83e99c9 100644 --- a/ja/Days/day61.md +++ b/ja/Days/day61.md @@ -23,7 +23,7 @@ Now we could use `kubectl` as we have showed in previous sections. But there are ### Simple Kubernetes Demo -Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](/Days/IaC/Kubernetes/kubernetes.tf) +Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](2022/Days/IaC/Kubernetes/kubernetes.tf) In that file we are going to define our Kubernetes provider, we are going to point to our kubeconfig file, create a namespace called nginx, then we will create a deployment which contains 2 replicas and finally a service. diff --git a/ja/Days/day65.md b/ja/Days/day65.md index 2478bf4..e7bb7fb 100644 --- a/ja/Days/day65.md +++ b/ja/Days/day65.md @@ -58,7 +58,7 @@ tasks: We are going to use Vagrant to set up our node environment, I am going to keep this at a reasonable 4 nodes but you can hopefully see that this could easily be 300 or 3000 and this is the power of Ansible and other configuration management tools to be able to configure your servers. -You can find this file located here ([Vagrantfile](/Days/Configmgmt/Vagrantfile)) +You can find this file located here ([Vagrantfile](2022/Days/Configmgmt/Vagrantfile)) ``` Vagrant.configure("2") do |config| diff --git a/pl/day46.md b/pl/day46.md index 71dced4..f564043 100644 --- a/pl/day46.md +++ b/pl/day46.md @@ -154,7 +154,7 @@ This is also a great resource for samples of docker-compose applications with mu In the above repository, there is a great example which will deploy an Elasticsearch, Logstash, and Kibana (ELK) in single-node. -I have uploaded the files to the [Containers folder](/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` +I have uploaded the files to the [Containers folder](2022/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` ![](Images/Day46_Containers15.png) diff --git a/pl/day60.md b/pl/day60.md index b88ace4..12bcdb1 100644 --- a/pl/day60.md +++ b/pl/day60.md @@ -58,7 +58,7 @@ You can find out more information on the [Docker Provider](https://registry.terr The above is a very simple demo of what can be done with Terraform plus Docker and how we can now manage this under the Terraform state. We covered docker compose in the containers section and there is a little crossover in a way between this, infrastructure as code as well as then Kubernetes. -For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](/Days/IaC/Docker-Wordpress/docker-wordpress.tf) +For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](2022/Days/IaC/Docker-Wordpress/docker-wordpress.tf) ``` terraform { diff --git a/pl/day61.md b/pl/day61.md index 4b15932..74b4b7a 100644 --- a/pl/day61.md +++ b/pl/day61.md @@ -23,7 +23,7 @@ Now we could use `kubectl` as we have showed in previous sections. But there are ### Simple Kubernetes Demo -Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](/Days/IaC/Kubernetes/kubernetes.tf) +Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](2022/Days/IaC/Kubernetes/kubernetes.tf) In that file we are going to define our Kubernetes provider, we are going to point to our kubeconfig file, create a namespace called nginx, then we will create a deployment which contains 2 replicas and finally a service. diff --git a/pl/day65.md b/pl/day65.md index 2478bf4..e7bb7fb 100644 --- a/pl/day65.md +++ b/pl/day65.md @@ -58,7 +58,7 @@ tasks: We are going to use Vagrant to set up our node environment, I am going to keep this at a reasonable 4 nodes but you can hopefully see that this could easily be 300 or 3000 and this is the power of Ansible and other configuration management tools to be able to configure your servers. -You can find this file located here ([Vagrantfile](/Days/Configmgmt/Vagrantfile)) +You can find this file located here ([Vagrantfile](2022/Days/Configmgmt/Vagrantfile)) ``` Vagrant.configure("2") do |config| diff --git a/zh_cn/Days/day46.md b/zh_cn/Days/day46.md index 00b5b5c..f21e9bb 100644 --- a/zh_cn/Days/day46.md +++ b/zh_cn/Days/day46.md @@ -154,7 +154,7 @@ This is also a great resource for samples of docker compose applications with mu In the above repository there is a great example which will deploy an Elasticsearch, Logstash, and Kibana (ELK) in single-node. -I have uploaded the files to the [Containers folder](/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` +I have uploaded the files to the [Containers folder](2022/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` ![](Images/Day46_Containers15.png) diff --git a/zh_cn/Days/day54.md b/zh_cn/Days/day54.md index 10b78ae..563826e 100644 --- a/zh_cn/Days/day54.md +++ b/zh_cn/Days/day54.md @@ -29,7 +29,7 @@ In this first step we are simply going to create a stateless application within In the first demo we want to define everything we do with YAML, we could have a whole section on YAML but I am going to skim over this and leave some resources at the end that will cover YAML in more detail. -We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](Days\Kubernetes\nginx-stateless-demo.yaml) +We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](2022\Days\Kubernetes\nginx-stateless-demo.yaml) ``` apiVersion: v1 diff --git a/zh_cn/Days/day60.md b/zh_cn/Days/day60.md index 61b4dbf..374a83b 100644 --- a/zh_cn/Days/day60.md +++ b/zh_cn/Days/day60.md @@ -58,7 +58,7 @@ You can find out more information on the [Docker Provider](https://registry.terr The above is a very simple demo of what can be done with Terraform plus Docker and how we can now manage this under the Terraform state. We covered docker compose in the containers section and there is a little crossover in a way between this, infrastructure as code as well as then Kubernetes. -For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](/Days/IaC/Docker-Wordpress/docker-wordpress.tf) +For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](2022/Days/IaC/Docker-Wordpress/docker-wordpress.tf) ``` terraform { diff --git a/zh_cn/Days/day61.md b/zh_cn/Days/day61.md index c3c819b..83e99c9 100644 --- a/zh_cn/Days/day61.md +++ b/zh_cn/Days/day61.md @@ -23,7 +23,7 @@ Now we could use `kubectl` as we have showed in previous sections. But there are ### Simple Kubernetes Demo -Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](/Days/IaC/Kubernetes/kubernetes.tf) +Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](2022/Days/IaC/Kubernetes/kubernetes.tf) In that file we are going to define our Kubernetes provider, we are going to point to our kubeconfig file, create a namespace called nginx, then we will create a deployment which contains 2 replicas and finally a service. diff --git a/zh_cn/Days/day65.md b/zh_cn/Days/day65.md index 2478bf4..e7bb7fb 100644 --- a/zh_cn/Days/day65.md +++ b/zh_cn/Days/day65.md @@ -58,7 +58,7 @@ tasks: We are going to use Vagrant to set up our node environment, I am going to keep this at a reasonable 4 nodes but you can hopefully see that this could easily be 300 or 3000 and this is the power of Ansible and other configuration management tools to be able to configure your servers. -You can find this file located here ([Vagrantfile](/Days/Configmgmt/Vagrantfile)) +You can find this file located here ([Vagrantfile](2022/Days/Configmgmt/Vagrantfile)) ``` Vagrant.configure("2") do |config| diff --git a/zh_tw/Days/day46.md b/zh_tw/Days/day46.md index 00b5b5c..f21e9bb 100644 --- a/zh_tw/Days/day46.md +++ b/zh_tw/Days/day46.md @@ -154,7 +154,7 @@ This is also a great resource for samples of docker compose applications with mu In the above repository there is a great example which will deploy an Elasticsearch, Logstash, and Kibana (ELK) in single-node. -I have uploaded the files to the [Containers folder](/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` +I have uploaded the files to the [Containers folder](2022/Days/Containers/elasticsearch-logstash-kibana/) When you have this folder locally, navigate there and you can simply use `docker-compose up -d` ![](Images/Day46_Containers15.png) diff --git a/zh_tw/Days/day54.md b/zh_tw/Days/day54.md index 10b78ae..563826e 100644 --- a/zh_tw/Days/day54.md +++ b/zh_tw/Days/day54.md @@ -29,7 +29,7 @@ In this first step we are simply going to create a stateless application within In the first demo we want to define everything we do with YAML, we could have a whole section on YAML but I am going to skim over this and leave some resources at the end that will cover YAML in more detail. -We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](Days\Kubernetes\nginx-stateless-demo.yaml) +We could create the following as one YAML file or we could break this down for each aspect of our application, i.e this could be separate files for namespace, deployment and service creation but in this file below we separate these by using `---` in one file. You can find this file located [here](2022\Days\Kubernetes\nginx-stateless-demo.yaml) ``` apiVersion: v1 diff --git a/zh_tw/Days/day60.md b/zh_tw/Days/day60.md index 61b4dbf..374a83b 100644 --- a/zh_tw/Days/day60.md +++ b/zh_tw/Days/day60.md @@ -58,7 +58,7 @@ You can find out more information on the [Docker Provider](https://registry.terr The above is a very simple demo of what can be done with Terraform plus Docker and how we can now manage this under the Terraform state. We covered docker compose in the containers section and there is a little crossover in a way between this, infrastructure as code as well as then Kubernetes. -For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](/Days/IaC/Docker-Wordpress/docker-wordpress.tf) +For the purpose of showing this and how Terraform can handle a little more complexity, we are going to take the docker compose file for wordpress and mysql that we created with docker compose and we will put this to Terraform. You can find the [docker-wordpress.tf](2022/Days/IaC/Docker-Wordpress/docker-wordpress.tf) ``` terraform { diff --git a/zh_tw/Days/day61.md b/zh_tw/Days/day61.md index c3c819b..83e99c9 100644 --- a/zh_tw/Days/day61.md +++ b/zh_tw/Days/day61.md @@ -23,7 +23,7 @@ Now we could use `kubectl` as we have showed in previous sections. But there are ### Simple Kubernetes Demo -Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](/Days/IaC/Kubernetes/kubernetes.tf) +Much like the demo we created in the last session we can now deploy nginx into our Kubernetes cluster, I will be using minikube here again for demo purposes. We create our Kubernetes.tf file and you can find this in the [folder](2022/Days/IaC/Kubernetes/kubernetes.tf) In that file we are going to define our Kubernetes provider, we are going to point to our kubeconfig file, create a namespace called nginx, then we will create a deployment which contains 2 replicas and finally a service. diff --git a/zh_tw/Days/day65.md b/zh_tw/Days/day65.md index 2478bf4..e7bb7fb 100644 --- a/zh_tw/Days/day65.md +++ b/zh_tw/Days/day65.md @@ -58,7 +58,7 @@ tasks: We are going to use Vagrant to set up our node environment, I am going to keep this at a reasonable 4 nodes but you can hopefully see that this could easily be 300 or 3000 and this is the power of Ansible and other configuration management tools to be able to configure your servers. -You can find this file located here ([Vagrantfile](/Days/Configmgmt/Vagrantfile)) +You can find this file located here ([Vagrantfile](2022/Days/Configmgmt/Vagrantfile)) ``` Vagrant.configure("2") do |config|