Datasets:
willtheorangeguy
/
2022-SelfHosted-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
7
369
[1823.96 --> 1825.08] right now,
[1825.12 --> 1825.46] at least,
[1825.46 --> 1826.50] is using a...
[1826.50 --> 1827.54] So you can actually...
[1827.54 --> 1828.34] This is a really neat trick
[1828.34 --> 1828.90] that I didn't know
[1828.90 --> 1829.58] until this morning.
[1830.36 --> 1831.48] You can put in
[1831.48 --> 1832.64] your Ansible config
[1832.64 --> 1835.98] the vault file location
[1835.98 --> 1836.96] as a script.
[1837.36 --> 1838.70] And in that script,
[1838.88 --> 1839.74] you can actually have it
[1839.74 --> 1841.40] do the Bitwarden CLI
[1841.40 --> 1843.24] export lookup
[1843.24 --> 1844.24] thing of the password.
[1844.78 --> 1845.96] And then it returns it
[1845.96 --> 1846.42] as a string,
[1846.50 --> 1847.16] which then feeds
[1847.16 --> 1847.88] into the
[1847.88 --> 1850.06] rest of the process.
[1850.50 --> 1851.66] So all I'm doing,
[1851.66 --> 1852.36] I haven't moved
[1852.36 --> 1853.18] any of the secrets
[1853.18 --> 1853.86] themselves
[1853.86 --> 1854.82] out of Ansible,
[1854.98 --> 1855.60] out of the vault
[1855.60 --> 1856.24] in Ansible,
[1856.56 --> 1857.84] but I've moved
[1857.84 --> 1859.24] the vault password
[1859.24 --> 1860.80] from a local text file
[1860.80 --> 1861.64] on my laptop
[1861.64 --> 1863.26] into Bitwarden.
[1863.42 --> 1864.20] And now I've connected
[1864.20 --> 1864.84] the two together
[1864.84 --> 1865.86] using Orange's post.
[1868.12 --> 1869.02] Very nice.
[1869.30 --> 1870.28] We'll have links to this
[1870.28 --> 1871.56] so you can follow along.
[1871.64 --> 1872.22] We'll have links to this
[1872.22 --> 1872.68] in the show notes,
[1872.76 --> 1873.00] of course,
[1873.10 --> 1874.54] at selfhosted.show
[1874.54 --> 1875.28] slash 71.
[1875.86 --> 1876.30] I thought it'd be
[1876.30 --> 1876.82] really difficult,
[1876.98 --> 1877.58] but it turned out
[1877.58 --> 1878.72] to be about a five
[1878.72 --> 1879.90] or ten line change.
[1880.42 --> 1881.04] There'll be a commit
[1881.04 --> 1882.52] in the show notes
[1882.52 --> 1883.04] if you're curious
[1883.04 --> 1884.20] just to how easy it is.
[1884.62 --> 1885.18] Easier than getting
[1885.18 --> 1886.34] the recipe app going.
[1887.10 --> 1887.78] Much easier.
[1887.84 --> 1888.14] Yes.
[1891.14 --> 1891.82] We love you,
[1891.86 --> 1892.10] Tandor.
[1892.14 --> 1892.62] We love you.
[1893.06 --> 1893.46] We've been having
[1893.46 --> 1893.94] a lot of fun
[1893.94 --> 1894.38] on the Discord
[1894.38 --> 1895.34] over the last couple
[1895.34 --> 1896.40] of weeks with Ansible
[1896.40 --> 1897.20] and Infrastructure's
[1897.20 --> 1897.86] Code Talk,
[1897.92 --> 1898.90] as you can probably tell
[1898.90 --> 1899.76] from how much
[1899.76 --> 1900.50] of it's in the show.
[1900.98 --> 1901.78] One of the things
[1901.78 --> 1902.62] I decided to do
[1902.62 --> 1903.54] when Brent was here,
[1903.88 --> 1904.86] he just flippantly
[1904.86 --> 1905.56] asked me,
[1905.76 --> 1907.28] can you do DNS
[1907.28 --> 1908.28] from your Docker
[1908.28 --> 1909.08] Compose generator?
[1909.52 --> 1910.00] And I was like,
[1910.28 --> 1910.62] sure.
[1911.54 --> 1912.34] Knowing full well
[1912.34 --> 1912.92] I couldn't,
[1913.02 --> 1913.62] but how hard
[1913.62 --> 1914.34] could it be, right?
[1914.34 --> 1916.06] It turned out
[1916.06 --> 1917.40] to be quite
[1917.40 --> 1918.36] the operation.
[1918.52 --> 1919.00] It took me about
[1919.00 --> 1919.84] two or three days
[1919.84 --> 1920.34] with the help
[1920.34 --> 1921.16] of about four
[1921.16 --> 1922.06] or five people
[1922.06 --> 1922.54] on Discord
[1922.54 --> 1924.34] to write possibly
[1924.34 --> 1925.16] one of the most,
[1925.42 --> 1926.42] dare I say it,
[1926.42 --> 1927.68] over-engineered
[1927.68 --> 1929.00] Ansible tasks ever.
[1929.38 --> 1930.20] This thing essentially
[1930.20 --> 1932.04] takes a traffic label,