 Hello, everybody. Welcome back to another technical demo around the purpose application. My name is Daniel Ho. Today, I'm going to showcase around the running focus faster with the Quickstars on developer sandbox. So what is the developer sandbox? The developer sandbox fundamentally provides developers with probably open space environment in a shared and multi-tenant open space cluster, which is a pre-configured server developer tool. For example, core-ready workspace is Web IDE application environment environment. And the developer can easily create containers from their source code from Game Reparatory or even Dockerfile, as well as build a new application using sample application with the stacks provided. And developer can also add services to share the database from existing open-shifted template catalog, what you probably have charted. And there are so many benefits from a developer sandbox. It's a free cluster that the developer only needed to do is sign up the Red Hat developer website. So let's get started. So here, you can access the developer sandbox using Red Hat's link in the slash dev dash sandbox. When you access the developer sandbox, you need to first sign up a free, credentialed developer Red Hat.com website. And after that, you can just log in with your credential. And then at a time, your developer sandbox cluster will be speeded up in the next five minutes. So once you enter the developer sandbox and go to OpenStick developers console, you can find the multiple in the videos. You can find the various quick start, how to get started, your application to the developer and deploy a specific solution with the app-punched container platform. So here is a new corpus quick start here. So get started with the corpus-using ham chart and then getting started with the corpus-using such as the immediate build. And then you could already find another existing one, the corpus application binding. Using corpus quick start is to bind your corpus application to streaming, such as the app-chip cap card. So today, I'm going to go through two quick start brand new ones that could get started with the ham chart and S2I build. Okay, let's get into the demo. Okay, first of all, as I already mentioned earlier, let's do access the URL, and right-hand slash depth dash sandbox. Once you access the URL, you can find all detail of what is sandbox and there are some practice, how to use that and what kind of benefit you can have as a developer. And then click on get started the sandbox. I already signed up. So after you sign up, you just click on start your sandbox and then redirect to a login page with the single sign on and just click on developer sandbox. Once you log in, open up the cluster and then you can just go to quick start to click and then find the corpus related quick start here. And then there are three quick starts already built in your developer sandbox. So let's try to get started with the corpus using S2I build. As you see, there are six steps to finish this quick start enablement. And then also you can find what kind of benefit you can have with the corpus application development like a container first and unified configuration. Let's try to click on the first step, create a new corpus application. The first step is click on the perspective switcher like a developer standpoint and click on add menu and then you can find the multiple perspective you can get starting like a simple application from get your part of it, what that file, et cetera. Well, with the developer sandbox, you already have two namespaces like your username dash then username dash stages. So you don't need to create a new one. It's already limited resources for you. So we just use that namespace. Click on get to improve your application. Here's a sample example, corpus application with a quick start and the container directory is getting started. You can actually add any other give-it-part you want, but just follow this quick start just using an existing example. You can create the more computation here, for example, a hash check or a resource limit. So once you click on hash check, you can add your ridges and write this problem. Once you click on create button, the corpus cannibal icon just shows up, which means your corpus application got started to deploy opposite cluster with this username spaces and then you just check your world. So do you see the corpus application and do you see corpus deployment, et cetera? You can just make sure everything is working along with the quick start instruction. So click on the icon, you can find the deployment and et cetera. So go to next step, just a few view states. Once you click on the build icon and you can find the load detail, how build is working and then click on the last thing is to check your world. So you have to see the company status in the build load. It takes maybe a few seconds or a few minutes to complete the all build strategy. So during the build, the build process you're getting prior to in the main room packaging build and then containerize the application and push it into internal container registry. Okay, so move on to the next step. Just a view associated with priority to what kind of application is implemented. But the one of the beauty of the sandbox, we already installed the corpus space for your application development environments. So when you click on the corpus space icon, it will bring you to corpus space directly instead of go to get it properly. Which means the developer can edit your application for itself and deploy it back to the container platform right away. So it's the one of the beauty of the developer sandbox for the developer and once you develop the application deployed to approach the backhand force just like the cloud will develop in-bound. So just take a look at that, the guest started a project, you can find the hello and greeting endpoint and here is the CDR injection when you pass down a parameter and then it will return with a hello, something like output. Next step, you path status. In the new hover, your path icon, you can find the running status and we just success to path deployment. And then the next step and then the number five, the change the default icon with the corpus, the default is the Java icon. So with this application based on corpus framework, so we need to make sure this path based on corpus. In order to that, just delete the existing label and then the new label at the output.io slash and one time equal corpus. So there are already predefined icon to differentiate your multiple path in the same name space. So now you can see the beautiful corpus icon on your path. In the next step, so make sure everything is followed by your working and then the last step, we wanna make sure application functionality is working using URL and the endpoint, one endpoint hello, which will be return hello and another endpoint is hello, there's reading with some formula like my name is Daniel and then you can find that the return is a hello Daniel. It's a pre-working. So just a six step how to get started the corpus application development using developer sandbox as well as corpus.io spaces. So it takes just five minutes to learn how corpus works in developer sandbox. Let's try to do another quick start once again just for fun. Okay, this is starting with the corpus using hand chart. So hand chart is one of the popular to manage the configuration and runtime environment on Kubernetes cluster. So luckily we have hand chart already included in developer sandbox. For the most team perspective, they can define the standard corpus application on time environment from developer sandbox. Okay, so click on hand chart and just search for corpus and just create this hand chart to install and you can change the configuration from the GUI view or the YAML view, whatever you can select your preferred way. And then just click on hand chart. So there are a lot of configuration but we just use the default configuration along with this instruction and check your world to verify you're working. So as you see, you can find your new corpus application and you click on the detail, maybe you can find the image pool backup but don't worry about that. So click on hand chart to release UI, you can find the notification here. You might have some image pool error or image pool backup error because your view is still undergoing. So next step, you're gonna check it out your view process status, go to view log just like we did in the previous corpus S2Y quick start and you can find all detailed logs here and the ones to push its success and then your corpus application is not running on developer sandbox opportunity cluster. So I think it's a week done in the step two and then I just click on yes, everything is okay. And then next step, go back to topology view and the corpus department is working. I just checked it out once already and then click on yes and then go to next and the last step, just check all application functionally using a lot URL and then go to hello. In this application, you can see you're getting start application examples. So go to greeting, like a primary like a example hand, so hello hand. Okay, so today we're gonna run about corpus application department using quick start which he provided in developer sandbox. So now developer just sign up freely in the developer sandbox at developer.redhead.com and then they can actually develop a sandbox and go through a quick start how to develop corpus application using S2Y reload from your github property and you can actually use existing sample application but also a little more operation team perspective or even a devos team perspective, you can set it up your standard corpus runtime environment using ham chart, how to do that using quick start instruction. Thank you for watching. If you have a more interesting question around the quick start with the corpus and developer sandbox, please let us know. We are more than happy to address your question right away. Thanks again, have a good rest of the day.