 Hello and welcome. GitLab recently released two interesting features. First is the new WebID beta powered by the open source DS code and a remote development environment. And you can connect, pair the WebID with the remote development environment. In this demo, I'm excited to show you both features. My name is Itzigan Baruch. I'm a Senior Technical Marketing Manager here at GitLab. So let's see the new features. So this is the GitLab project. This is my source code. And you can see here the button for opening the WebID. And if you're already familiar with the old WebID, you will notice that the new default now has a new interface. And this is the better version of the new WebID. And this is only a minimal version with minimal features. What we are calling MVC. And the team is iterating and will add more and more features and the upcoming milestones. So let's see what exists today. So if you see on the left side, this is my project that is open because I opened this WebID on my project at GitLab. So I can see my code and we can see a few icons on the left side, which are for different tabs. First is the file explorer to open my code, a search or search and replace capability, and the version control where you can commit your code. We have here two tabs that currently in this version disabled. One is the running debug and extensions. And you can open settings to change things like a team. For example, if you want to change the color or if you want to have any other settings that the VS Code provides, for example, if you want to change the font size or other settings that you want to make in the editor. So let's see a quick flow. So I will create a folder and I will open the contextual menu, which is a nice feature that wasn't available in the previous editor, that you can create a new file. So finding files, easy remain files or folders. So I will just create a new file. I will write something. All right. And I can also do a drag and drop of this file if I want to make it out from the test folder to the root of the repository or return it back to the test folder. And let's see how you can research now and use the search to look for the world. There are ops and immediately find it here and I can now replace it with stack ops. And even it presents to me side by side the original and what I want to change. And so I will change it. And in this version, we can search on multiple open files and the team may plan to enable this search capability for any file in the project. So we added a change to the repository. So now let's commit it to a new branch. So we will add here a commit message. So and commit and push it to the repository and you can create a new branch or use commit to the main branch. So I will commit to a new branch. And here I can add a name for the new branch or just click enter to get to accept a different name. And now I committed on the bottom right. You can see a new pop up success. Your changes have been committed and I have three options. I can continue working with this editor to go to my GitLab project or create merge request. So I will just create a merge request, assign myself and click the create and request button. And as you notice, because I pushed a new change a pipeline already immediately started to build and test my change. So now I want to show you the second part is how I can connect to the remote development environment not for my web browser, but not on my local machine on my remote development environment where all of the runtime environment the dependencies everything will be installed on a remote development environment on any cloud and me as a developer will not need to install anything locally on my machine. So I will start by opening the terminal and configure the remote connection. And the first step is to provide a domain URL to the remote development environment. And in this version, the developer needs to create or someone needs to create this remote development environment. Basically what you need is a VM on any cloud provider. And in our online documentation you can find under remote development you can see how to create this remote environment. Basically we prepared a docker image so you just need to run this docker command and it will create for you the docker image on that VM and it will include anything that you need in order to connect from your web ID. So I have already such a remote development environment so I will add the URL and here now I need to provide the path to the project in that environment and I need also to provide a connection token also in the online documentation you can see how you can generate this certificate. All right, so now by clicking this button I am switching from working on my local machine into this code server based which is installed on my remote development environment. Great, so now if you notice I have a new project. This is my source code that is installed in the remote environment. I can continue working now and get immediate feedback and everything will be done on that machine. And if I want, I can open a terminal to the machine. This can be useful to have to install anything if you want, if I want to install any dependencies on that machine or view a log file so anything that I want I can now form my web ID for my browser have a secured access to that remote machine. So let's run a few commands like see what we have and if I want for example to see the content of the engine X here I can I see the content of the engine X and I can do I have a full flexibility to work on the project and the full terminal access and this what I just show you is just the beginning if you want to learn more about our planning and the team roadmap of this feature you can open our handbook page and see the maturity plan. So what I've just showed you is the minimal maturity level which allows you to connect between the local web ID to the remote development environment but here you can see the full world map until this feature will be leveled by our end users. So with that I will conclude the demo hope you find it interesting and I encourage you to try it yourself and thank you for watching.