GitLab Source Code Group, 27 Jan 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Getting started with GitPod / GDK

Description

A guide to GDK/GitPod features.

A

Welcome to part two connecting to the git pod jdk for this part of the demonstration, I'm not using a gitlab employee account, and so I'm using instead.

B

A

Gitlab, regular user account created on gitlab.com, which will require forking the main gitlab repository. So let's go ahead and do that.

A

Here's the main repository, I press the fork button fork it to my local namespace and off. It goes I'll. Just stop the video here. This will take a little bit of time to complete.

A

Okay, now that the fork has completed, we can go ahead and start using gitpot, so we go over here to the skid pod. But if it's not visible, we just press the drop down and switch between the web ide and gitpod. It is visible. So I will click the gitpod button and I'll be asked to log in with gitlab, because this is the first time that I've used gpog with gitlab I'm going to authorise against my gitlab account. This is a one-time action. You won't need to do this after the first time.

A

Okay, so gibpod is now building the virtual environment in the cloud. This will take probably at least seven or eight minutes I'll. Stop the video here and we'll come back to that when it's finished.

B

Right here we are in gitpod.

A

Gdk, so here we have full access to the entire source code in our fork of of gitlab or jdk, and also down here we have a running application. So if we go to the gdk window, we can see, for example, the status of the jdk, and we can see that's great. All the services are up. We could do a tail.

B

On the logs fantastic, we could also have a look at the database.

B

Yep lots of tables there.

A

We could even just perhaps open a new terminal window and run some regular unix commands.

B

So, let's grab this oops. Let's look for a particular string.

B

Validate deploy; okay in the app folder.

B

And there it is okay.

A

So importantly, we can go to this open ports, tab and it has all the ports that have been used by the various gdk services, including the web front, end. So there's two ways of looking at that: I can just click open preview and I'll get this kind of inside the application window or or and or I can also run it in a regular tab by pressing open browser- and here we are so what's the login. If I go back.

B

Here the gdk- let's just close- that we don't need that now.

A

We can scroll up, and the password has actually been echoed here.

B

A bit further back now.

B

No okay, we've gone.

A

Too far back okay well, the password is, it will be printed when you first log in, but it's basically boot.

B

And then it's five.

B

uh L, I f e, that's the standard password for um the development environment. So what we'll do is we'll just log in here root password, it's going to ask us for to change the password once we log.

B

B

Okay, so I'm going to be asked to change my password.

B

I'll change the password and all good okay. So now I can log in.

A

And this entire development environment is running on git pod and it's still accessible to me, though, externally, okay.

A

Finally, if I could even run a particular uh spec, if I wanted to from the command line um the faster way, well, the more thorough way would be to run it from the ci. But I can go and pick up a spec.

B

So, let's just grab something um anything really.

B

I've got this one.

B

We'll go to it, you can just close, it go to a turbine window.

B

Bundle fix here.

A

A

And that'll take a little minute to boot, the full rails environment. But it's actually going to go ahead and run.

B

Our spec for us, okay, so.

A

That's pretty much it in terms of a tour and in the next tutorial, we'll just show you how to do a merge request and submit it back to the main branch.

A