text stringlengths 0 2.46k |
|---|
[3124.82 --> 3126.44] sure that it's really you logged in. |
[3126.62 --> 3130.94] So when you're working on that code space in the browser, it's tied to your GitHub account. |
[3131.18 --> 3135.66] So you can't use a code space anonymously or like at this point, it's just going to be |
[3135.66 --> 3136.40] tied to you. |
[3136.40 --> 3141.78] So as long as like you authenticated into GitHub.com or you authenticated into the extension, |
[3142.02 --> 3143.68] then you're going to be authed and secure. |
[3144.24 --> 3146.66] Speaking of that, are you too afraid to GitHub, Jared? |
[3146.92 --> 3148.88] Do you feel like you're social engineering me right now? |
[3148.98 --> 3152.38] I mean, I want to know because I mean, at this point, you're outing yourself to be maybe |
[3152.38 --> 3153.38] insecure potentially. |
[3153.52 --> 3155.40] So get secure if you're not too afraid. |
[3155.92 --> 3157.02] I'm not going to answer that question. |
[3157.30 --> 3157.58] Okay. |
[3158.30 --> 3164.72] So if you are working locally in VS Code inside a dev container, the code is in the container, |
[3164.72 --> 3165.06] right? |
[3165.06 --> 3167.20] And you can you mount it locally somehow. |
[3167.52 --> 3169.90] VS Code handles whatever dance that is. |
[3169.90 --> 3175.16] And then you as long as it has local credentials for SSH or however you're authoring against |
[3175.16 --> 3180.66] your remote origin, whether it's GitHub or some other provider, as long as you have access |
[3180.66 --> 3184.92] to that in your local system, it's just going to pass that through or use that directly. |
[3185.06 --> 3187.04] It should be pretty straightforward. |
[3187.04 --> 3187.44] Yep. |
[3187.44 --> 3187.96] Yep. |
[3188.18 --> 3194.62] And you can use the same if you're using Git or GitHub commands via terminal or via extensions |
[3194.62 --> 3198.78] in VS Code, then you can install or use the same ones in your container and get that same |
[3198.78 --> 3199.82] access and authentication. |
[3200.56 --> 3200.84] Okay. |
[3201.54 --> 3203.16] It's almost too good to be true, Adam. |
[3203.42 --> 3203.76] Almost. |
[3203.76 --> 3205.48] Is it not true? |
[3205.48 --> 3207.34] Because usually when it's too good to be true? |
[3207.80 --> 3208.72] Not true. |
[3209.10 --> 3211.22] Going back to these templates. |
[3211.56 --> 3215.74] So I'm looking at the Go one now in the official dev containers templates repo. |
[3215.94 --> 3217.40] The Go template. |
[3217.40 --> 3222.46] And it's pointing that there is no Docker composed. |
[3222.66 --> 3224.20] There's no Docker even in the template. |
[3224.50 --> 3228.74] It's just like pointing at variants of an image. |
[3229.00 --> 3231.78] There's no image URL that I can even see. |
[3232.10 --> 3235.56] Documentation URL, license URL, image variant. |
[3236.04 --> 3240.94] Does this have built into it knowledge of this default repository of images perhaps? |
[3240.94 --> 3248.02] Because it looks like it's going to be pulling from a Microsoft hosted thing. |
[3248.62 --> 3254.50] Image, mcr.microsoft.com slash devcontainer slash go, according to this. |
[3254.80 --> 3258.30] So I guess Microsoft is hosting a bunch of these images for people. |
[3258.42 --> 3264.76] And if you don't specify anything like specific image URL or a Docker file that grabs an image |
[3264.76 --> 3268.06] itself, it's just all falling back to Microsoft hosted stuff. |
[3268.16 --> 3269.48] Is that, am I reading this right? |
[3269.48 --> 3275.22] Yeah, so the set of templates that we host as part of the spec are all going to reference |
[3275.22 --> 3277.86] images that we're also publishing as part of the spec. |
[3278.04 --> 3283.30] So if you go to github.com slash devcontainers, then slash templates or slash images, |
[3283.30 --> 3286.66] you'll be able to see the corresponding templates and images that we're publishing. |
[3287.56 --> 3290.34] And in the templates, so for instance, the Go one that you pulled up, |
[3290.72 --> 3294.94] that image property is pointing to the Microsoft Container Registry or MCR, |
[3294.94 --> 3298.58] which is where we're publishing our first party spec images. |
[3298.58 --> 3304.54] And we try to just make it simpler of, hey, our templates just need to reference that image. |
[3304.64 --> 3308.34] That way you don't have to worry about like, oh, I need to manage additional files or like know how |
[3308.34 --> 3309.88] to work with or add a Docker file. |
[3310.06 --> 3314.06] But if you want to use a Docker file or your project already has a Docker file, you can totally |
[3314.06 --> 3314.78] use that too. |
[3314.90 --> 3320.10] You would just move that image property over to your Docker file instead of in the devcontainer.json |
[3320.10 --> 3322.98] and then have your devcontainer.json point over to your Docker file. |
[3323.62 --> 3323.74] Right. |
[3324.44 --> 3325.26] No, I mean, I love that. |
[3325.34 --> 3326.52] It's sensible defaults. |
[3326.52 --> 3328.10] You're actually providing a service here, right? |
[3328.14 --> 3333.76] Like you're providing an image repository that people can download images from in the case that |
[3333.76 --> 3338.20] they don't have their own or pointing at Docker Hub, which is what many images currently |
[3338.20 --> 3345.84] hosted on Docker Hub or elsewhere, that it makes the getting started for the simplest case is |
[3345.84 --> 3346.84] pretty straightforward. |
[3347.00 --> 3353.92] Like if you're at, if your code is just using go 1.19 or 1.18, you can just take this template, |
[3354.12 --> 3359.84] drop it in your folder, devcontainer.json, maybe add a customization or two, maybe not. |
[3360.14 --> 3363.66] And you can have a devcontainer with go installed ready to run your code. |
[3364.38 --> 3365.22] Yep, exactly. |
[3365.22 --> 3369.86] I mean, who doesn't want to have a go machine one click away a cent? |
[3369.94 --> 3371.08] I mean, that's, that's how you get there. |
[3371.12 --> 3374.20] It's like, is this, it's like, we had said that conversation with Matt, basically. |
[3374.62 --> 3375.68] We were talking about that though. |
[3375.72 --> 3379.80] We were just like saying how allergic we are to just rando installs to different things. |
[3379.80 --> 3380.92] And like, right. |
[3381.02 --> 3385.96] If I'm not, if I'm go curious, which a lot of the go time audiences, there's a lot of people |
[3385.96 --> 3389.66] who are in the go world and they just don't even mind, you know, they drop things on their |
[3389.66 --> 3391.44] path that whatever, go binary or whatever. |
[3391.56 --> 3392.54] Yeah, it's already set up. |
[3392.68 --> 3392.84] Yeah. |
[3392.84 --> 3395.06] But if you're go curious, you're like, how does this work? |
[3395.06 --> 3399.32] You can just spin up a go container via dev containers, play around. |
[3399.32 --> 3403.40] And like your local machine is the same as it was, you know, when you close that machine |
[3403.40 --> 3406.78] down, when you close that container down, it's, it's right there, which I think is super |
[3406.78 --> 3407.08] cool. |
[3407.22 --> 3412.68] I mean, I just love, you know, the ephemeralness of it, but also the permanence in how the dev |
[3412.68 --> 3417.56] container spec lets you specify so much to use it within teams and different organizations. |
[3417.56 --> 3423.60] I guess the real interesting thing is how is it when it goes beyond like us nerds, right? |
[3423.64 --> 3425.68] Like we geek out on this stuff, right? |
[3425.70 --> 3426.86] This is great to us. |
[3427.18 --> 3431.08] But what about when my son who's seven is at school, right? |
[3431.08 --> 3434.42] And he wants to go into this class, which he's now in some GT classes and they're doing |
[3434.42 --> 3435.22] computer things. |
[3435.22 --> 3439.62] Well, you know, I don't know if it's that mature yet, but I would have got, I got to |
[3439.62 --> 3444.20] imagine that like the teacher isn't going to want to have to set up every single machine |
[3444.20 --> 3448.12] and do all these different things for six or seven different computer environments that |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.