GitHub GitHub Universe 2022 - Cloud, 21 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Codespaces—Git coding fast - Universe 2022

Description

Codespaces helps you get coding faster and focus on building what matters together. In a single click, launch any GitHub repository with your favorite editor—backed with compute and terminal access—customized with your themes, preferences, and dotfiles. April Leonard will show you how to explore, contribute, and start coding with infinite, isolated, secure, and fast developer environments.

As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub

Thanks!

Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github

About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com

A

Thank you, hey everybody. What an incredible kickoff for Universe in case you missed it! I'm April, Leonard staff, software, engineering manager and Technology moves fast, but working at GitHub. We build tools to help.

A

You move even faster, so today, I'm going to show you how to get coding faster with code spaces, terrible pun, I know, couldn't help myself, but code spaces solves problems that you don't realize you have, we don't think twice about checking out code downloading dependencies and then fighting with dependency conflicts, installing tools and then debugging bad interactions with other tools and then switching branches and the constant maintenance of our developer environments.

A

The good news is that, with code spaces, you never have to worry about any of this ever again, just select a repository and go you get a clean, isolated, pre-configured environment with the power of configures code.

A

So let's take a moment to talk about the evolution of software and how revolutionary this is.

A

If we have a bug that we want to fix like a change that we want to make, how do we get that into the hands of our users?

A

Back in the 2000s early 2000s, like the odds, I, don't know it was a long time ago. I was an engineer on a team deploying an on-premise solution, which meant we packaged up our code.

A

We pre-installed it on a tower and we physically shipped it to the customer's Business site time to confidence in my change was months, and then we pivoted to software as a service model hosting our code and data centers and responding to change was much faster at this point and then, with the rise of cloud, hosted Services, we moved away from our data centers and we offloaded the maintenance burden of procuring hardware and patching servers to keep up with the latest security and firmware upgrades one more step of simplification and then Docker and kubernetes came along to help us isolate and scale our applications, and this brought our developer environments.

A

One step closer to production. I might fix multiple bugs in a day. Each of these moments and Technologies fundamentally shifted how developers work and yet, with all these improvements, we still struggle with works on my machine.

A

When I started at GitHub two years ago, I struggled for days to get my environment set up with our 10 year old Ruby monolith to debug my issues, I needed to figure out like what on my machine, was different from the other 600 Engineers, who all had slightly different setups I, looked at what recent OS upgrades I might have done what processes were running and whether Docker was allocating enough memory.

A

There were so many permutations of what could go wrong. That I was ready to table flip I'm supposed to know how to do this stuff right and then we adopted code spaces, your developer environment in the cloud spaces, automates, environment, setup, it hands you a fully built and ready machine. That is exactly the same every time in seconds.

A

So, instead of comparing production to each of those 600 Engineers machines, you only have to compare them to one at any point in your git history and it works on every machine in every tool and for everyone.

A

Since we made code spaces available to GitHub teams at Enterprises last year, we're seeing users onboard their teams faster and improve their developer experience. But, of course this is GitHub and we want to make this experience available to everyone.

A

So in case you missed it this morning, I'm thrilled to announce again that code spaces will be available over the next week for all GitHub users, with up to 60 hours of free usage every month.

A

So excited so we don't want to focus on fighting with our developer environments. We want to focus on building what matters, but with your experience, your tools, Wherever You Are, with the best practices of config as code built in so let's Dive In.

A

The first thing I'll show you is that that you can create a code space from any Repository. So, for example, this is a little react project that I'm working on from the code drop down.

A

Usually I would clone locally, but instead I can simply switch to the code spaces tab and by pressing this little plus button, I can create a code space.

A

Now I already have a code space running on this Branch right here, but if I switch branches, let's go over here to Main and let's try Implement checkout there we go back to the code drop down. Then the code spaces takes this into account. So really I can have as many code spaces on as many branches as I want or really from anywhere in your git history.

A

You'll also find that code spaces are now in the top navigation header, so we'll go ahead and click on that and we land on the code spaces dashboard. Here we have access to these quick start templates, a curated list of getting started experiences and then a list of the code spaces that you can sort by Repository.

A

So first, let's create a blank code space when I click that button a developer environment is spinning up in the cloud pre-installed, with an image that we call the universal image. It has a common set of tools and runtimes like python, node, Docker and even ml libraries like conda and pytorch.

A

We maintain the image so that you don't have to keep up on the latest tooling and security patches go ahead and zoom in here a little bit, so you can see a little better resize this window. The best part about templates is I, didn't Fork a repo.

A

So if we show the hidden files here in the room root is what I meant to say in their root directory, so I'm going to type in ls-la.

A

It's going to show our hidden files as soon as we get connected here so make sure I'm hardwired in which I am.

A

I'll give this just a moment there. We are all right, ls-l-a and there you can see that um you might recognize that there's no get folder the blank template doesn't even initialize git. So it's a completely clean environment, just like local. That I can just like mess up and delete when I'm done and code spaces loads. Your experience, so our DOT files are loading. I have my GitHub theme here and my vs code. Extensions are installing so right here in the bottom right hand corner you should be able to see that I've got Copilot.

A

So, let's, let's create a file called test.

A

Js and I'm, going to ask Copilot to create a nested Loop three levels: deep.

A

All right, I think copilot's not actually installed. I'm just gonna just take a minute here.

A

Copilot, where are you hey, co-pilot that doesn't that's not working on my item? I didn't actually get that started all right. What I I will say: I'm really confused, but that's okay. Sometimes this happens. That's what happens in live demos. That's how you know it's live! That's why I'm doing it like this right! Thank you. Thank you very much.

A

All right, okay, copilot you're with me, are you with me: co-pilot, a nested loop, three levels deep and thank you. Thank you, co-pilot much better, all right! Well, so you're gonna laugh right because the whole point I wanted to do. That was that I could show you that my indent, rainbow uh extension is also loaded, especially I. Think it's not, but that's, okay, um so, uh and then. Lastly, what I can tell you is loaded.

A

Is uh you might notice here it says like this beautiful JS, that's material uh icon or my material icon theme, which I just always like to have, because it shows me all of my file types at a glance so um so I showed you like the extensions that I love right. You're gonna have the extensions that you love um but code spaces. Also loads, my DOT files, so my favorite tools are always with me. For example, I'll start a new.

A

Actually I can just leave this same terminal window, but I'm going to start a new session. A new tmac session called new. Let's call it Universe demo, all right, so there I have my tmex session started and I'm going to type in a new window, and, let's start top over here right so like I, can have top on one side and I can have my favorite processes.

A

My favorite Windows, like my setup, wherever I want, and so because I this all loaded through my DOT files, you can actually share productivity tips with anyone simply by sharing your dot files repository and that's really powerful for teams right. My experience, if somebody if you're pairing with somebody and they're like oh, that's, really cool you can just be like here, it is and your dot files are automatically loaded with code spaces because, as developers we get very attached to our tools and for every project. I have a slightly different setup.

A

So often it's vs code in the browser, it's all I need. But let's take a look at our options because code spaces integrates with your favorite tools. So what we're going to do is we'll switch back to the code spaces dashboard right over here and we'll just refresh the page that we can see that new blank template that we're just working on together.

A

I go right over here to the triple dots in the bottom right hand, corner press open in- and you can see here that we have vs code in the browser we have vs code desktop and now we also have in data jet brains and Jupiter lab.

A

So if you're a Vim user, you can also connect to your code space directly from the GitHub CLI, like this ghcs SSH that stands for GitHub code spaces SSH, and it just gives us an automatic list of all the code spaces that we want. So let's go ahead and look at our automatic waffle here, which is the one that we just created together and now we have a terminal attached to our code space so from here.

A

I can even view that tmux session that we just started by typing tmux session, Dash, T and I- think we called it Universe demo. There we go.

A

You know it's the exact same machine in the cloud and the CLI is a powerful tool for managing your code spaces. So I'll switch to a new session over here and let's take a look at ghcs, which shows us all of the commands that we have available. So we can copy files between your local machine and your code space.

A

We have crud operations, you can manage the visibility of your ports and even rebuild the CLI, provides you incredible access to your remote machine in the way that works for you and the ability to automate common scripts and full access to the codespaces API. So codespace really meets you where you are on any device with the browser. So I can switch seamlessly between my laptop and my tablet, depending on whether I'm working at home heading to the coffee shop or on my commute all right.

A

So next we're going to spin up a little next.js project together, I'm sure many of you have already done this before, because next is super cool. But if you haven't traditionally, we would start with something like this: the docs.

A

Now it's a lot of steps that we're going to have to walk through um and even if you haven't looked at nexjs before it's pretty much the same with any technology right, there's a guide, there's a blog or a readme to get you started.

A

But what if I told you there's a better way that automates these steps for you? Let's take a look at spinning up a next repository, the code spaces way so frame your code, spaces dashboard, we'll go here and select the see all link.

A

And we can see all these templates that we have available so we'll simply select the next JS template and that's it. That's all the steps and it just works behind the scenes. We're spinning up a remote environment, we're downloading the code from the backing repository installing dependencies running the application and displaying the output and we're connected to a code space now, npm, Dev, sorry, npm, run Dev is running automatically and the core files that drive this experience are opening too.

A

So I don't know about you, but it might seem a little bit like magic, but it's just config as code right next to your project. The dev container Json file is a document that defines how your project will build, display and run. So, let's take a look while the server is finishing, running I'll, open the dev container folder here and we'll bring up. Dev container Json actually make this a little bit smaller and it's a little bigger there.

A

You go there, you go um so what we do here is we specify the minimum post requirements the build the file that should open on launch and which processes to start and which ports to forward so every time that someone creates a code space from this repository, they get the same exact, delightful experience.

A

I have the power full power of vs code in the browser with my terminal and my running application, and since index.js is the file that drives this experience. It's already open I, don't have to remember whether it's index.js or app.js or hashtag JS I can just make a quick change, and here let's call it: um where is our fast? Let's call it universe, Universe demo, and how about getting us a nice um emoji and there it goes I, I, actually didn't even press save and we see our change right away.

A

So, instead of sitting back and consuming information about how to explore new Frameworks I get to spend more time tinkering and playing with the code, you might have noticed that Source control is tracking our changes. You can tell from the source control tab over here. That's right, so we act. We have git initialized, but we still didn't create a fork of this repository.

A

It's not connected to a repo until we decide to turn this project into something more so I can commit my change, excellent and yes, I do want to Stage it and I can create a repository. Let's make it public and I'll call it. My next idea.

A

So now I can start building out my project with actions depend about pull requests and all the other tools that I need to start. Iterating I didn't even have to break out of my coding flow and now I'm ready to collaborate.

A

I'm partnering with my friend Burke, who is a vs code expert here, to show you a little bit more about the magic of code spaces in vs code, Hey, Bert, I, just pushed up this new repo called Next idea. Let's Jam On It.

B

How's it going thank you, April, hey folks. My name is Burke and I'm being asked to log into the VPN and I'm just going to decline that right away, I work with the vs code team at Microsoft and uh yeah, let's Jump Right In here and get started now. The first thing we'll do is dismiss this window again and then come up here and see about turning this off. Let's just disconnect perfect problem solved, nope, okay, VPN or no VPN. Normally.

B

What we'd have to do here is we'd have to come Fork right and then we come over click, the code tab we come over and we clone we'd, pull it down locally. We wouldn't we read the readme, because we don't need that.

B

uh We do some Googling 30 minutes later we'd give up and actually read the readme and then maybe we'd be up and running, but today we're not going to do any of that, we're just going to click code and then we're going to go to code spaces and we're going to create a code space right here in the browser now I feel like in the interest of full disclosure. I should tell you I do work on the VSCO team at Microsoft and so I'm a little biased, I love vs code, I love vs code.

B

This is my vs code. This is my local vs code, you're. Looking at it here. This is my theme. It's called cobalt2 you're, welcome to steal that use it for yourself. It's a beautiful theme. I've got tons of icons here in my activity bar including things I use a lot like Docker and Azure. All my extensions are here even more disturbing. My sidebar is on the right. I mean y'all. Look this thing's totally customized I can order pizza directly from my vs code right, there's literally an extension for everything. That's the magic of vs code.

B

Now listen! This may seem strange to you, but for me this is home I'm comfortable here and if there's one thing that we know on the VSCO team, it's that it's not our vs code. It's your vs code! It's what you do with it! That makes it great and having that familiar environment is like a warm blanket for your soul when you're jumping into a new project or code that you've never seen before and with vs coding code spaces. You can take this experience. Your experience with you, no matter where you are.

B

Let me show you how envious code from the gear, we'll click on turn on settings sync, and then from here. We have some options on what we want to turn on settings. Are things like your sidebar on the right keyboard shortcuts any shortcuts that you've defined in a user Snippets that you've defined or tasks for running projects?

B

All of your extensions can be synced and your UI state, which is things like your themes, so we'll just sign in and sign in with our GitHub account and you'll see this happens pretty quickly and our settings are now synced up to GitHub. Now, how does this actually work in the real world? Let's toggle back over to our browser, and here you see the same project that April had, but it's running for me with my settings right. So this is my vs code running here in a code space, my sidebar is on the right.

B

I got my nice theme here again, that's Cobalt, 2 I can't can't say that enough. It's a great theme. You should use it if you're not using it's awesome, great ones out there. That's my fave now. Another thing that we just added uh in vs code is a secondary sidebar, because you like the first sidebar so much. We added a second one for you and so I actually toggle this with a custom keyboard command and I like to put my find in the in the secondary sidebar right.

B

I want it to have a dedicated spot, and if you don't notice about Visual Studio code, you can literally just take things and drag them around to where you want them to be and just drop them. Okay and everything in vs code works this way. So, for instance, if we're looking at the timeline in vs code, it shows the history of the current file that we're in and you may think to yourself. Yeah, that's cool, but that would make more sense in the source control view.

B

No problem just pick: it drop it over here right here on the source, control View and you can literally customize vs code and make it exactly the way that you want it to be Now by default. We do a one-way sync for all of your settings when you turn settingsync on to your code space, even if you haven't turned it on in your code space. So one time one-way.

B

Sync, if you want a true two-way sync, you can come and turn on setting Sync here in the browser the same way we did locally and now any changes you make in the browser will be reflected everywhere else. You have settings, sync turned on all right now: I, don't know anything about next, but that's great. uh It appears I don't have to it just kind of works, but I do know a little bit about react.

B

So what I want to do here is just kind of jump in and make a change and see if we're going to start working on this project.

B

So, let's see, let's jump over to our index file here and what I want to do is create. uh Let's just add, maybe an H2 here, so we'll just do an H2 and just say hello from vs code.

B

uh There we go. uh Oh, it failed to compile. Did it how about now? That's what I thought all right, so hello from vs code now I. Would uh this is great I like this, but I'd love to change the color of the font, but I can't remember how to do that in react. I always forget this.

B

um Oh, this is embarrassing because it's a demo, but you know what we do have full vs code here, and that means that we can take advantage of things like copilot. So maybe, if we just ask copilot for an H2 with inline Style, uh perfect, that's exactly what I wanted. Yes all right! So this is a red H2. It's an object. I always forget that copilot is great at helping you with the little things so we'll just say hello from vs code, all right.

B

So now you know what I've decided: hey I, really like this I'm going to work on this I want to invest some time into this.

B

We could do that right here in the browser we could have 50 code spaces running at one time, if that's what we wanted to do, but sometimes, if you have a long running, work stream right, you're going to invest in something long term, you might want to bring that and work on it locally and you can seamlessly move from the browser to your local vs code from the menu by selecting open in vs code desktop.

B

This will reload our local vs code and connect directly to that code space. Now, when this code space comes up, what you'll notice is that, even though we're local down here in the left hand corner if I can zoom in a bit, you can see we're actually connected to code spaces. That's called the remote indicator and that's how we know if I toggle that sidebar you can see, we've got the sidebar here locally and eventually all of this will sync because we turned on setting sync in the browser as well.

B

We can also run this locally, just like we did in the browser. So if we go over to our ports, we can open up our application here in the browser and if you notice here we might still be, are we still firing up? Let's see here, 's our terminal, yeah I think we're still we're still compiling. But if you notice here, it's going to run it right here on this 127, so it Everything feels local, even though you're actually running in a code space and that's the magic of working with code spaces.

B

So now you have your your own environment, the place where you feel comfortable, but all of this has happened in the span of a couple of minutes in the real world. You might do this a lot because code spaces are super easy to spin up and then knock down they're very they can be very ephemeral environments, and so you can manage those from github.com and you can do it directly from Visual Studio code.

B

So with the code spaces extension here I'm going to come over, we can see all of my code spaces that I have created at the moment for all of the accounts that I've got so here's the one we're working on. You can see it's green because it's actually running and we can do things here like delete a code space. We can even add a code space from here.

B

You can paste in the URL to a GitHub repo or we could just go search, GitHub right here from Visual Studio code and create a new code space best of all y'all. We can change the machine type. Look at this. We can get 32 cores and 64 gigs of RAM. Yes, you can literally upgrade your development environment with one click that is the magic of code spaces all right.

B

So, let's connect connect back to this code space we were in now, we've talked a lot about customization and how important that is- and it is important for you as an individual, but it's also important for code spaces itself.

B

So when April was talking before she mentioned, this configuration is code and that allows us to configure this environment the vs code environment. For anyone who creates a code space from this repository so, for instance, I, have the eslint extension it's installed for me locally, but if I could put it in the code space, it would improve the experience for anybody who uses this project, and we can do that with a right click and then saying add to Dev container Json.

B

Now, when we do this, it will add the configuration to this file here. So let's take a look at that and if you scroll down, you can see it's added this section here specifically for vs code, and any extensions will be in that extensions array. Furthermore, we can specify any setting for vs code here in this configuration file.

B

For instance, if we figure everybody's sidebar needs to be on the right, we could do that. Don't do that! That's not very nice. Don't move people's sidebars, although I do it. Instead, what you should do is it's really good for doing things like eslint?

B

Certain properties of this extension always show status. Let's set this to true that way. Everybody can always see the status of eslint in their status bar, which will be nice now. What we want to do is we want to go ahead and check this back into April's repo so that she can get the benefits of the eslint extension and the settings that we've added here. But if you remember, we never actually forked this repo right. We just started coding. So how does this exist if I commit code? Where does it go?

B

I, don't know, let's find out so I'm going to come here to the source control. This was our change that we made we'll go ahead and get rid of this and let's go ahead and Commit This, Dev, container file and we'll just say, add eslint config and commit now. We've committed this file, we're ready to sync: it sync it to what well, uh because it's Visual Studio code in code spaces. We take care of this for you.

B

So if we look back at our terminal here- and we do a git remote you'll see that that's not a valid command. Oh, oh, by the way you see that little light bulb right. There look at this. We actually fixed commit. If you click on it says, did you mean to run git remote V? Why, yes, I did thank you very much. Visual Studio code, uh okay, so there we have, an origin has been set for us and the Upstream right. This has all been configured for me.

B

I didn't have to do any of this, so now uh let's go ahead and push and what I want to do is I want to create a pull request. So normally we might jump out and go to github.com and do that. We could still do that, but with the GitHub issues and pull request extension right here in the sidebar, which is included in the code space, we can create a pull request right here from Visual Studio code.

B

So right here from this sidebar, we should be able to create a pull request directly against you know we should do, though. Probably what would be better is if we created a feature Branch there we go update, config all right and then maybe we will publish this Branch into the origin and we'll submit a PR on that one. Instead, all right so I managed to get my git in a state where I can't push the branch or create the PR, but uh you can create PRS directly from Visual Studio code.

B

Excuse me right here with the GitHub issues: pull requests and issues extension uh even manage them from Visual Studio code, uh bringing everything into the inner loop into the place where you feel comfortable.

B

So that's Visual, Studio code and code spaces. It's your vs code! Take it with you, no matter where you are or where you're working, happy coding, April.

A

Thanks Burke I'm so excited to learn how your changes are going to make me more productive, So. Speaking of learning, there are tons of ways to learn and explore new languages and Frameworks and I'm excited to share with you today that LinkedIn learning has over 50 courses integrated with code spaces. They cover six of the most popular programming languages, as well as topics like data science, AI machine learning. These courses will be unlocked on LinkedIn learning for free through February 2023, so definitely go and check it out.

A

I know I'm going to, but I want to tell you about a little bit earlier in my career when I was also still learning how to code. I had my own office, it was a long time ago. I would spend most of my day coding without interruption, right, I'd close my door, but today I, don't close my door on my teammates.

A

We work together like Burke and I, were just collaborating and learning from each other and that's why it's not just about building what matters but doing it together and code spaces makes it really easy to collaborate, whether you're working in real time working, asynchronously or with the larger open source community.

A

So let me show you we're going to head back over to our next idea and sometimes I have someone like Burke who I'm pairing on the code with but other times, I just want to show off my work to my product manager or designer now code spaces are secure by default, which means they're private. So, let's go over here to the ports Tab and we can see here.

A

Our visibility is private, but I'm going to go ahead and right click go to my port visibility and I can actually make this public or private just to my organization, so I click, this I'm, making this port, private and I can go to this preview, and now I can actually share this link with anybody and I mean you could actually like go to this link right now and you can share your work as it's in progress and have somebody execute that running application and give you feedback right there. Another way that I can real time.

A

Collaborate is with the live share extension, so back here in our code, I can go to live share and I can now share in real time. I can invite people to collaborate directly on this code. Space with me live, or we can invite a bunch of people and start a party programming session. I, don't know if party programming is a thing, but you've heard it today. So once my project gets a little bigger, I I'm going to start getting more collaborators right, I'm going to want to start managing code space.

A

Managing my changes with pull requests and since the GitHub CLI is automatically installed in the Universal image, I can create a PR directly from the command line, so I don't even have to break my coding flow, we'll go to the terminal window, start a new terminal window. Thank you and ghpr, and there it is I can just create.

A

Do anything I want to right here with PRS, so sometimes I think about code spaces like get stash, but it's for my entire laptop, so we're going to go ahead and stash our project next idea, because I want to show you really quickly what it's like when I collaborate with my team at GitHub and how code spaces integrates into my workflows.

A

So this is a map of my team. We are split across time zones, so real-time communication isn't always possible. We rely heavily on asynchronous collaboration, which we do through pull requests. In fact, right now, let's go ahead and take a look at a pull request for my team, one of my team members Emerald so back here at my demo.

A

Now I don't want Emerald to get blocked with getting these improvements. In but when I'm in the flow, it can be really hard to switch contexts.

A

So, instead of when I'm working locally stashing my changes, switching branches, maybe rebuilding I, simply go to any pull request like this one from Emerald I select the code drop down right here and I create a code space from her last commit.

A

This is another one of those friction points that I didn't realize that I had until code spaces handed me a completely isolated and pre-built environment at exactly the right point in git history, so I can switch context more easily, but there's another place that I'm contributing to PRS another place where we build together and that's the open source community code spaces is a game changer for open source for maintainers and contributors alike. So this demo that I just showed you is incredible for keeping maintainers, productive and reviewing PRS.

A

You can spin up as many laptops in the cloud as PRS to review, making it easier to juggle and manage all the incoming requests and once that PR is merged, delete the code space and, if you're a contributor, think about this, every project has a slightly different structure and tool set and oftentimes are complex and you have limited time to contribute.

A

So, let's take a look at an open source project and really dig into that complexity.

A

All right um code spaces manage manages complexity so that you don't get stuck halfway through configuring, your environment, with support for complex project types, powerful machines, easy configuration and fast, continuous rebuilds, there's a rich and Powerful tool set for maintainers and contributors to make the community better for everyone all right. So we're going to check it out here with a repository called questdb. It's an open source project, a high throughput time series database that I've been tracking because I'm a total data.

A

Nerd and I've been working on this code space from a fork of this project on a new branch called bootstrap code spaces, I've added a dub container Json file, and this is a Java project by the way. So, if we scroll down here, you can see it's like 88, Java and I was a Java developer. In my past life and my primary IDE was IntelliJ. So when I'm coding in Java it's my preferred tool.

A

I can come up here to the code drop down, I can select open in and let's select the jetbrains Gateway excellent, so you figured out exactly which code space I want to create and I. Just want you to call out here that we also have access to Ruby mine, pycharm, PHP webstorm and go land, so I'll leave IntelliJ connected and we'll Jump Right In, so I get the power of code space of IntelliJ without even having to install the IDE or Java on my machine.

A

That's right in all my developer tools, except for a Thin Client, are located in a secure and isolated remote environment. So I don't ever have to worry about Java conflicts ever again, so in our IntelliJ run configuration configurations they're already loaded, so we can simply come up here and run the server now with this. Well, what this will do is it's going to spin up a web console so that we can interact with our database, it's right over here at localhost, 8 000. But, as you know, this is actually running in the cloud.

A

So this is our beautiful web console is like one of my favorite things about questdb. It's really really nice to use and I'm going to go ahead and I've got some preceded data here, I'm going to run and awesome, there's our data. So in a few seconds, we're up and running and exploring this project now, one of the things that I tend to do when jumping into a new open source project to contribute is figuring out what the critical paths are and how the project is formed now a powerful way to do.

A

This is finding a test, and that does something important and then at a break point and you can just Trace to the stack. So let's not do that together. Now, if we come back here to uh the test that I picked out, which is the SQL compiler test, I'm glad I'm guessing just taking a guess that my class under test here is SQL compiler. So let's go ahead and search for that and there it is so it looks like yeah. We've definitely got um we're constructing a new SQL compiler right here.

A

So let's go to the top of this test and I put a breakpoint already here in our SQL compiler excellent I'm going to go ahead and right click and let's debug this test.

A

This is what I love about code spaces. Did it go nice, okay, so I am terrible about reading code. I am an active learner. I want to play with the Technologies, not just read about them. So I've hit my break point. I can start investigating the stack trace and build a mental map from the connections right, I'm ready to jump into a good first issue. So, like, let's think about that right, we went directly from starting our environment. We found a test and we're just up and running now.

A

Quest UB runs in a single Docker container, but what about Mono, repos and microservices codespaces supports these two. So here I'll show you back at our um questdb Repository so from here questdb we're going to spend most of the rest of our time in this code drop down in these three little dots right here and now. What we can do is create a code space but with options.

A

So from here you can see that we have multiple Dev containers to work with. So if you're working on a mono repo, you can Define multiple dead containers in the same repository, so each collaborator can work on a code space tailored to their needs. Now, if you remember I seated the quest database with some data, and so if you have different teams working on the same code code base and they had different data needs- that they're working on all you need to do is create a new, so they're working on different components of the system.

A

All you need to do is create a new Dev container and you have access right here to a different um kind of like a profile. It's like a different profile, so you have just like a different profile in your system and what, if I, have microservices that contain dependencies across multiple repositories? You can configure your Dev container to pull in those code bases as well leveraging GitHub authentication to ensure secure access, so GitHub has or code spaces. Has all these complex cases covered and let's take a look at our machine type.

A

Here we have access to 4, 8, 16, 32 cores and also in private beta six cores as well super powerful machines, you'll notice here two cores aren't available because I set the minimum requirements in the dev container to four cores, because I just want to make sure that everybody who's spinning. This up has a really great experience all right.

A

So now we talked a little bit about these multiple Dev containers. I actually want to show you just how easy it is to configure a Dev container. So we're going to come back here in our code drop down to these three little dots and we'll configure a Dev container.

A

Stud containers are truly powerful, but they're also super easy to configure. So from our repository here we go you can see. This is the dev container that I was already working on for this project.

A

um You I, let's say yeah like if I just kind of start typing some important information here, you're going to see some squiggles. That's because we go ahead and we're we're making sure that that we're um parsing this file, but what I really want to show you and I want to draw your attention to is this features.

A

Section features are reusable configurations kind of like building blocks that help you configure your environment with common Frameworks language, support and tools. So for an example right here you can see that this is SSH is is what we're loading in here. So if we type SSH, you can see that this is an SSH server which allows remote connections from the terminal and it's created by the dev container core team, and it has the blue check mark so that we know it's been verified now. I have the documentation in line right here.

A

If we click on that right here, so I can just copy it right over and we already have this one access, but yep copyright over and there it is, and I can build my Dev container in this way. Now we also if we go back here, we can see that we could bring in Java. We can bring a node Python and for each of these images it has tons of versions right. So this is really powerful. You don't have to have your own image.

A

You can take advantage of the pre-configured images and tools that you need and the dev containers team will handle all of the versions for you and all of those tools, so I can build out. My Dev container I can also do this Pro tip in vs code and rebuild right in line and iterate on my environment, all right. So the last thing that I want to show. You is actually we'll go ahead and cancel out these changes. The last thing that I want to show you is oh wait.

A

There we go they're code drop down there, we go from these. Three dots is setting up rebuilds.

A

Prebills are give you the ability to run um post spaces incredibly quickly. It's like continuous integration for your developer environment and it's all powered by actions.

A

So, depending on the size and complexity of your project, it might take a few minutes, but maybe much longer to create your environment, so you can create as many configures configurations as we like. So let's take a look at one hmm so for each configuration you can tie it to a branch and you can create as many as you want here.

A

You can also set the triggers that you need on every push on every configuration change and you can really configure it for your needs based on the regions that you want, or the number of templates that you want to maintain, and so, if we select simply clicking to see the output of one of our configurations, you can see that this is actually powered by action. This is right here in the tab, so you can click in and debug on any configuration and make sure that successful or debug it.

A

If it's not in the last seven days over 600 branches, the average time save pre-building was about 10 minutes, that's 10 minutes for every developer, who didn't have to pull, build and run we just let computers do what they're good at automating away our soil.

A

B

Now you know a little bit more.

A

About the types of problems that code spaces can solve for you, the keystrokes that you can see and how to get in.

B

A

Speaking, you've been really productive. Today, nice work y'all. We certainly got coding fast. You.

B

A

Of prototyping, we started a PR review. We.

B

A

Up a complex, OSS project to contribute back to the community, you know all nurse paper post faces has fundamentally changed my workflow for the better. You know that feeling of getting a new laptop and being simultaneously extended through being slate and annoyed at the bottom setting it up. We didn't ask them both ways. Every time you part started those face, it's new and fresh and clean. Yet you have just what you need to get productive quickly and focus on the most important in your job. Part of your job building awesome projects so whether you're working.

B

A

A side project starting.

B

A

New or working on a complex application for work or open source, try and code spaces out and get coding faster. Thank you.

A