 I'm Arti from ThoughtWorks and we're going to talk about development and environment set up with Waygrid. So let me give you an example from my own experience. Some months back I was working on a large-scale application as part of a very big team and we faced three issues predominantly. Number one, what worked on my computer didn't work on my friend's computer. And number two, the QA has always complained that we were giving them broken code. And number three, the project manager started losing trust in us. Why was this happening? The project was very big, which means we had a lot of external dependencies. Lot of dependencies means lot of versions, which means the permutation and combinations of these versions and these dependencies means potentially every developer can have their own unique development environments. For example, someone used Apache, someone used Nginx. I'm sure you get the picture. So what we wanted was one development environment which can be repeatable and shareable across all developers in the team. So what did we do? We used Waygrid. I'm guessing most of you would have already heard of Waygrid, but still. Waygrid is a software which is written in Ruby. It's an open source software. It can be used to run on a virtual machine like VMware, VirtualBox, or Amazon EC2. So what we can do is use a tool like PuppetChef or Ansible to actually provision our code on these machines. So we will actually explain and show us a demo. Okay, let me show you how we can use Waygrid to set up our machine to have a development environment. To use Waygrid, basically we need Waygrid and VirtualBox to be installed in our machine. And then we just need to import the base box and then run Waygrid up. We will have a VirtualBox running our machine. But in order to have an environment for project development, we still need to write our own configuration so that we are able to have a customised box for the development. So here is the project and the configuration I'm using for this purpose. Here is the Waygrid file I write for project for Ruby development. In this file, I'm using a pre-set box as a base box and forwarding port 3,000. And also, I'm supporting a file synchronisation. But this is not enough. We still need to automate the process of installing different tools like RBM and Ruby. So I'm also using some provisionals that Waygrid is supporting. Waygrid is supporting multiple provisionals. For example, the Chess, Perpy and also Docker. And here I'm using Perpy modules to install them. And here is the Perpy script I write. In this script, I'm installing RBM, Ruby, Rails and all the other installations automatically. So after I get all this configuration ready, I'm able to have my VirtualBox running in my machine. And this one, I already have a box running here. Here is my box running here. I already have a box running. And also, I already have my sample project inside my folder. And this one is a Ruby project. So now I can access it into my box. As I mentioned before, my box is supporting file synchronisation. This means I'm able to have my project running project. I'm able to modify my project inside my local machine and then I'm able to run it within the box. So now I can easily access the same file as what I can see in my local machine. And here is my Rails project and then start running the server. And now I can see it. Yeah, it works. So now, I think you already have an idea how background can help us to help, can simplify the process of all the installations. Firstly, we only need to have a configuration file so that background can help us to do all the installation automatically. And this configuration file is able to be shared among the team so that all the team members can have the same settings. And also, it doesn't require much technical knowledge. So all the team members, including people like testers and test designers and project owners are able to have their box running and can see their project locally. What's more, for background, we know it's written in Ruby. So it can be quite flexible. We can always write our own Ruby gems and use them as plug-ins for Wegrad. So I think after you start using it, you will explore more benefit easily. Thanks, Shu Wei. If you want to see our sample lab or the code that we have written, you can find it over here. And if you have any questions, suggestions or feedback, please feel free to write us on those email IDs. Thank you.