text
stringlengths
0
2.29k
[1775.10 --> 1781.58] I was going to say, it'd be crazy if you actually just had that version in the Readme and it read it in the Image Go, which you probably could do because it's Go code.
[1781.68 --> 1782.40] It could do that.
[1782.46 --> 1783.00] Yeah, it could do that.
[1783.02 --> 1785.18] It doesn't sound smart, but it just would be interesting.
[1785.34 --> 1785.66] Yeah, no.
[1786.12 --> 1786.94] You want it in code.
[1787.26 --> 1788.04] Yeah, you want it in code.
[1788.04 --> 1788.44] Yeah.
[1788.44 --> 1788.96] Yeah.
[1789.20 --> 1795.70] And not to mention that when it's in code, by the way, we can have, again, we still need to figure this part out, I suppose.
[1796.18 --> 1798.48] But we could have things that automatically bump it.
[1798.74 --> 1801.08] When a new version comes out, it bumps it in code.
[1801.24 --> 1802.54] The pipeline bumps it everywhere.
[1803.12 --> 1805.96] And because the pipeline runs, it checks if the new version works.
[1806.24 --> 1808.54] And then opens up a PR and then we can just merge.
[1808.92 --> 1809.64] That's it, Jared.
[1809.78 --> 1810.22] That's it.
[1810.50 --> 1810.96] That's it.
[1811.08 --> 1811.36] Okay.
[1811.48 --> 1813.82] See, it's stuff like this that gets me really excited.
[1814.18 --> 1814.68] You're getting me.
[1815.18 --> 1815.50] Yeah.
[1816.32 --> 1816.66] Okay.
[1817.40 --> 1818.08] So that's cool.
[1818.68 --> 1823.46] How does that play into the other thing which happened recently?
[1823.74 --> 1824.92] Thanks to Chris Eggert.
[1825.02 --> 1836.74] And we, by the way, by the time this episode goes out, we will have shipped an episode of the changelog with Bridget Murtaugh from the dev container spec, from the VS Code team, talking all about this, in which Chris gets multiple shoutouts.
[1836.74 --> 1839.06] So he's probably getting sick of hearing us talk about him at this point.
[1839.06 --> 1848.32] He opened up a pull request, allowing us to run our code base on code spaces by adding a dev container.json.
[1849.16 --> 1850.34] So thanks to him for that.
[1850.40 --> 1852.76] He's using a Docker compose file and a little bit of JSON.
[1853.06 --> 1855.02] And you can just, like, say, open in code spaces.
[1855.02 --> 1856.30] And it's super cool.
[1857.30 --> 1860.24] How do these changes affect his work, if at all?
[1860.28 --> 1861.60] Or what's the integration there?
[1861.68 --> 1863.18] Because now we have, like, a dev environment.
[1863.34 --> 1865.80] We have this image that you're changing the way it works.
[1866.22 --> 1866.32] Yeah.
[1866.68 --> 1867.88] It all builds on top of it.
[1867.88 --> 1868.92] This is brilliant.
[1869.06 --> 1870.26] So this is brilliant.
[1870.80 --> 1871.24] It is.
[1871.90 --> 1872.86] And it's not me.
[1873.08 --> 1875.18] It's the combination of people that came together, right?
[1875.20 --> 1877.74] I wasn't expecting Chris, you know, to come along.
[1878.08 --> 1878.74] Nobody was.
[1878.92 --> 1880.00] I was, like, great.
[1880.04 --> 1880.62] It was amazing.
[1880.94 --> 1885.78] So based on that, that was pull request 437 in our code base.
[1886.28 --> 1894.20] I did a follow-up, 449, which basically changes the reference in the dev container with our runtime image
[1894.20 --> 1896.10] that is now pulled from GHCR.
[1896.46 --> 1900.36] And because you're running GitHub code spaces, that will be very fast.
[1900.88 --> 1903.08] Much faster than if you pull it from any other registry.
[1903.30 --> 1905.76] So that was another reason to go to GHCR.
[1905.76 --> 1907.00] So that works currently?
[1907.00 --> 1908.22] That's how it works currently.
[1908.22 --> 1910.80] If you go and open the file, come on, let's check it out.
[1910.98 --> 1915.18] Because I just did it last week in preparation for that conversation with Bridget.
[1915.30 --> 1921.38] And one thing I noticed is pulling from Docker Hub, just the entire, the first run code spaces experience.
[1921.38 --> 1924.24] I mean, it's probably five to seven minutes, you know.
[1924.48 --> 1925.42] That has improved.
[1925.72 --> 1928.86] The pull request I mentioned, 449, it no longer builds it.
[1929.26 --> 1932.32] It references the already built runtime image.
[1932.66 --> 1939.02] If you check out in the dev containers directory, if you look at the Docker compose file, line 5,
[1939.58 --> 1941.20] now has the image reference.
[1941.74 --> 1943.56] So the runtime image is no longer built.
[1944.34 --> 1946.30] The runtime image reference is pulled.
[1946.82 --> 1949.02] So it shouldn't take six, seven minutes anymore.
[1949.08 --> 1949.60] It should be instant.
[1949.60 --> 1950.72] I'll try that again.
[1950.72 --> 1951.42] There you go.
[1951.86 --> 1952.88] You let me know how well it works.
[1953.06 --> 1954.40] And if not, we'll work on it some more.
[1954.74 --> 1958.06] And all this stuff, all these things, we can start templating, right?
[1958.10 --> 1961.96] Once we get it like in the pipeline, there will be a single place where we declare those versions.
[1962.54 --> 1968.20] As soon as the image builds successfully, and because, you know, we like we go through the process in the pipeline,
[1968.84 --> 1974.72] we can start modifying all these other places, then build the production image, try and deploy it.
[1975.06 --> 1976.32] And if it works, we're done.
[1976.66 --> 1977.34] Where's the PR?
[1977.90 --> 1978.30] We're good.
[1978.30 --> 1981.20] Who else is doing it like this?
[1981.90 --> 1982.96] How state of the art is this?
[1983.66 --> 1984.14] I don't know.
[1984.22 --> 1990.06] I would say it's pretty cutting edge because we are redefining the CICD with Dagger.
[1990.22 --> 1990.84] We really are.
[1991.46 --> 1992.62] I mean, CICD is code.
[1992.74 --> 1993.92] Forget like any weird languages.
[1993.92 --> 1996.26] And some of the stuff that we have coming.
[1996.54 --> 1998.50] I mean, I can't talk about all the things.
[1998.50 --> 2001.60] But I like I'm like six months ahead.
[2001.82 --> 2003.72] And I'm so excited to be there.
[2003.90 --> 2004.84] And I'm so excited.
[2004.96 --> 2007.78] Like, for example, last Friday, it was just a few days ago.
[2008.30 --> 2009.72] We ship services support.
[2010.12 --> 2011.62] It's an experimental feature.
[2012.16 --> 2014.26] If you're listening to this, you're not supposed to use it.
[2014.26 --> 2015.04] So please don't.
[2015.16 --> 2015.42] Okay.
[2015.42 --> 2017.04] Because it may be broken in a number of ways.
[2017.10 --> 2017.62] We don't know.