text stringlengths 7 369 |
|---|
[1932.84 --> 1934.12] strips out with regex, |
[1934.32 --> 1936.50] a bunch of stuff |
[1936.50 --> 1938.30] surrounding the bit |
[1938.30 --> 1939.10] of data I want, |
[1939.18 --> 1939.76] which is, you know, |
[1939.76 --> 1940.74] the hostname of like |
[1940.74 --> 1943.20] test.jupiterbroadcasting.com. |
[1943.34 --> 1943.98] That's the bit |
[1943.98 --> 1944.76] I actually want, |
[1945.12 --> 1946.16] but I had to find a way |
[1946.16 --> 1946.90] to iterate over |
[1946.90 --> 1947.54] all the labels |
[1947.54 --> 1948.62] in the nested list |
[1948.62 --> 1949.62] that I have in Ansible |
[1949.62 --> 1951.68] and then extract them |
[1951.68 --> 1953.40] and do what I need to do |
[1953.40 --> 1954.58] and then only act on them |
[1954.58 --> 1958.54] when the item in the list |
[1958.54 --> 1960.42] was set to active equals true. |
[1961.22 --> 1962.40] There was a lot of logic in there. |
[1962.82 --> 1964.26] Anyway, the upshot is |
[1964.26 --> 1966.12] we can now specify |
[1966.12 --> 1967.94] for all of the self-hosted |
[1967.94 --> 1969.18] JB infrastructure |
[1969.18 --> 1972.36] simply by adding a container |
[1972.36 --> 1973.76] with a traffic label |
[1973.76 --> 1976.74] into our composed definition file, |
[1977.42 --> 1978.86] we add the DNS record |
[1978.86 --> 1980.68] automatically into Cloudflare. |
[1981.16 --> 1981.56] Hmm. |
[1982.06 --> 1984.68] That is pretty damn slick. |
[1984.78 --> 1986.48] So just by having the label |
[1986.48 --> 1987.36] for traffic, |
[1987.62 --> 1988.98] it figures out from there |
[1988.98 --> 1990.60] what the hostname should be |
[1990.60 --> 1991.06] and all of that? |
[1991.20 --> 1991.68] Absolutely. |
[1992.04 --> 1992.66] Yeah, that's it. |
[1993.22 --> 1994.62] And what's particularly fun |
[1994.62 --> 1995.74] is, you know, |
[1995.78 --> 1996.74] let's say I wanted to spin up |
[1996.74 --> 1997.90] an Nginx just to test, |
[1997.98 --> 1998.46] for example. |
[1998.46 --> 2000.00] I just copy and paste |
[2000.00 --> 2000.58] that in there |
[2000.58 --> 2001.72] and if I put test. |
[2002.02 --> 2002.90] As long as the domain's |
[2002.90 --> 2004.04] in my Cloudflare account |
[2004.04 --> 2005.16] or I have permissions, |
[2005.30 --> 2006.26] like you've given me |
[2006.26 --> 2007.56] delegated permissions |
[2007.56 --> 2008.66] on jb.com, |
[2008.80 --> 2010.02] I can add something |
[2010.02 --> 2011.10] into that Git repo |
[2011.10 --> 2012.68] and we could then theoretically |
[2012.68 --> 2014.20] have a continuous integration |
[2014.20 --> 2015.26] GitHub action |
[2015.26 --> 2017.00] that would pick up that change |
[2017.00 --> 2018.70] and deploy that new container |
[2018.70 --> 2020.56] and also the DNS records |
[2020.56 --> 2021.22] in Cloudflare |
[2021.22 --> 2022.60] automatically for us. |
[2022.84 --> 2023.98] Ha ha ha ha! |
[2024.36 --> 2026.08] That's what I'm talking about, Alex. |
[2026.14 --> 2027.20] That is awesome. |
[2027.20 --> 2028.00] It's really cool. |
[2028.10 --> 2028.88] That is awesome. |
[2029.00 --> 2031.02] And that is such a great example |
[2031.02 --> 2032.88] of, we recently were talking |
[2032.88 --> 2034.64] about Nix and Nix packages |
[2034.64 --> 2036.12] and managing Nix OS |
[2036.12 --> 2038.06] and all of that |
[2038.06 --> 2039.40] being a deterministic system |
[2039.40 --> 2040.72] and how it compared |
[2040.72 --> 2041.28] to Ansible. |
[2041.48 --> 2042.60] And this is such a great example |
[2042.60 --> 2043.68] where you can go much further |
[2043.68 --> 2044.12] with Ansible. |
[2044.26 --> 2045.02] You can go much beyond |
[2045.02 --> 2046.70] just what you can do |
[2046.70 --> 2047.14] with Nix. |
[2047.42 --> 2048.04] Very exciting. |
[2048.34 --> 2050.02] It makes me pumped |
[2050.02 --> 2050.90] to kind of redo |
[2050.90 --> 2052.12] some of this infrastructure stuff |
[2052.12 --> 2053.28] and do it like this |
[2053.28 --> 2054.10] from the beginning |
[2054.10 --> 2055.52] because, like, |
[2055.66 --> 2056.34] down the road |
[2056.34 --> 2058.16] it's just going to make |
[2058.16 --> 2059.04] future deployments |
[2059.04 --> 2060.50] so much simpler, right? |
[2060.68 --> 2062.04] That's really it. |
[2062.04 --> 2063.46] When you spin up a new show |
[2063.46 --> 2064.32] or decide you're going to |
[2064.32 --> 2065.20] have a garage sale |
[2065.20 --> 2065.98] or whatever it is, |
[2066.14 --> 2068.02] it's all automatic. |
[2068.38 --> 2069.18] That's so great. |
[2069.66 --> 2071.82] Yeah, and done once |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.