text
stringlengths
9
408
[2373.58 --> 2374.36] before your time,
[2374.46 --> 2374.64] Alex,
[2374.72 --> 2376.56] but in the old
[2376.56 --> 2377.40] init systems
[2377.40 --> 2378.14] of Linux
[2378.14 --> 2378.92] of yore,
[2379.44 --> 2380.32] there was like
[2380.32 --> 2381.38] this Zynet D
[2381.38 --> 2382.94] and what it would,
[2383.08 --> 2383.78] what it was
[2383.78 --> 2384.68] is it was like
[2384.68 --> 2385.12] this,
[2385.34 --> 2387.00] this master process
[2387.00 --> 2387.80] that would
[2387.80 --> 2389.36] open a port
[2389.36 --> 2390.12] on behalf
[2390.12 --> 2390.68] of a service
[2390.68 --> 2391.36] on your system,
[2391.36 --> 2393.08] but to save resources,
[2393.08 --> 2394.08] it would leave
[2394.08 --> 2395.12] the service stopped
[2395.12 --> 2396.74] until it received
[2396.74 --> 2397.36] a connection
[2397.36 --> 2398.56] on that port
[2398.56 --> 2399.70] and then it would
[2399.70 --> 2400.54] start the service
[2400.54 --> 2401.28] in the background
[2401.28 --> 2403.10] and forward the connection
[2403.10 --> 2403.92] and make it all
[2403.92 --> 2405.24] transparent to the end client.
[2405.38 --> 2406.48] So the first time
[2406.48 --> 2407.58] maybe it would be slow
[2407.58 --> 2408.36] for the end user,
[2408.50 --> 2409.78] but their connection
[2409.78 --> 2410.44] would get forwarded
[2410.44 --> 2411.22] once the service came on
[2411.22 --> 2411.96] and everything would connect
[2411.96 --> 2412.40] from then on,
[2412.42 --> 2413.14] it would be fast.
[2413.44 --> 2414.36] And what we need
[2414.36 --> 2415.20] is something like that
[2415.20 --> 2416.34] for Docker containers
[2416.34 --> 2417.42] because I have a similar thing
[2417.42 --> 2418.82] where I have containers
[2418.82 --> 2419.76] that I use a couple
[2419.76 --> 2420.68] of times a month,
[2420.68 --> 2422.34] but they're running 24-7.
[2423.66 --> 2423.72] Yeah,
[2423.72 --> 2424.04] I mean,
[2424.08 --> 2424.32] for me,
[2424.38 --> 2424.88] that's stuff like
[2424.88 --> 2425.64] Invoice Ninja
[2425.64 --> 2428.02] that I use to invoice clients.
[2428.38 --> 2428.60] You know,
[2428.64 --> 2429.36] I do it on a batch
[2429.36 --> 2430.28] once a month
[2430.28 --> 2431.04] and then it's running
[2431.04 --> 2431.78] for the entirety
[2431.78 --> 2432.76] of the rest of the month
[2432.76 --> 2434.40] and there's really
[2434.40 --> 2435.82] no reason for that.
[2436.30 --> 2437.54] So I'm sure
[2437.54 --> 2438.06] there are projects
[2438.06 --> 2438.74] out there to launch
[2438.74 --> 2439.62] containers on demand.
[2439.80 --> 2440.56] If you know of one,
[2440.76 --> 2441.34] please let us know
[2441.34 --> 2442.40] at self-hosted.show
[2442.40 --> 2443.36] slash contact.
[2444.16 --> 2445.04] I guess maybe
[2445.04 --> 2446.08] we could wrap up
[2446.08 --> 2448.00] our Docker Dazzle,
[2448.18 --> 2449.04] if you will,
[2449.36 --> 2453.30] with a talk about Dazzle
[2453.30 --> 2454.68] and a couple
[2454.68 --> 2455.20] of other things
[2455.20 --> 2456.12] like the fact
[2456.12 --> 2457.04] that Docker Compose
[2457.04 --> 2457.82] has some changes
[2457.82 --> 2458.38] that come in.
[2458.72 --> 2458.88] I mean,
[2458.88 --> 2459.56] we could just make it
[2459.56 --> 2460.54] a whole Docker
[2460.54 --> 2461.42] extravaganza.
[2462.34 --> 2463.54] I don't know,
[2463.64 --> 2464.04] maybe we start
[2464.04 --> 2464.98] with Dazzle.dev.
[2465.74 --> 2465.84] Yeah,
[2465.90 --> 2466.76] this one's pretty great,
[2466.82 --> 2467.06] actually.
[2467.18 --> 2468.28] It's a real-time
[2468.28 --> 2469.38] Docker container
[2469.38 --> 2470.00] log viewer
[2470.00 --> 2470.70] in the browser.
[2471.36 --> 2472.38] It doesn't require
[2472.38 --> 2473.84] anything terribly special
[2473.84 --> 2474.68] apart from mounting
[2474.68 --> 2475.38] the Docker socket,
[2475.38 --> 2477.00] so usual provisos
[2477.00 --> 2477.74] apply there