text
stringlengths
9
408
[2581.34 --> 2581.92] in terms of
[2581.92 --> 2583.22] this change here,
[2583.52 --> 2584.16] not a lot
[2584.16 --> 2584.92] is going to change
[2584.92 --> 2586.48] besides the invocation
[2586.48 --> 2587.18] that you need to
[2587.18 --> 2588.20] need to use.
[2588.56 --> 2589.84] Although they do say
[2589.84 --> 2590.66] that if you still
[2590.66 --> 2591.50] use the hyphen,
[2591.86 --> 2593.00] so Docker hyphen
[2593.00 --> 2593.56] Compose,
[2594.04 --> 2594.72] they're going to put
[2594.72 --> 2595.30] in an alias
[2595.30 --> 2596.00] that will effectively
[2596.00 --> 2597.52] just,
[2598.00 --> 2598.68] it will just continue
[2598.68 --> 2599.62] working as you expect.
[2600.46 --> 2601.14] There should be
[2601.14 --> 2602.46] full backwards compatibility
[2602.46 --> 2603.28] with existing
[2603.28 --> 2604.18] Compose files,
[2604.36 --> 2605.26] although there have
[2605.26 --> 2606.62] been some small changes
[2606.62 --> 2607.72] to the Docker Compose
[2607.72 --> 2608.14] spec.
[2608.66 --> 2609.84] So if you're seeing
[2609.84 --> 2610.20] errors,
[2610.34 --> 2611.52] that could well be why.
[2612.34 --> 2613.26] More than likely though,
[2613.30 --> 2613.90] it's probably your
[2613.90 --> 2614.90] YAML indentation
[2614.90 --> 2615.60] that you screwed up,
[2615.60 --> 2616.54] so make sure you enable
[2616.54 --> 2617.86] white space in your editor.
[2618.82 --> 2619.84] It's still in beta,
[2620.46 --> 2621.30] so, you know,
[2621.80 --> 2623.14] take that for what you will,
[2623.64 --> 2623.88] you know,
[2624.32 --> 2624.98] here be dragons,
[2625.10 --> 2625.94] all that kind of stuff.
[2626.86 --> 2628.22] But there are some
[2628.22 --> 2629.02] nice things in it,
[2629.26 --> 2629.46] you know,
[2629.56 --> 2630.48] largely though,
[2630.56 --> 2631.00] like I say,
[2631.10 --> 2632.98] it's a tech debt style,
[2633.56 --> 2634.56] addressing tech debt
[2634.56 --> 2635.28] style release,
[2635.44 --> 2637.50] and there isn't much
[2637.50 --> 2638.90] really in terms of
[2638.90 --> 2639.80] new features here
[2639.80 --> 2641.04] for normal people,
[2641.42 --> 2642.06] but the developers
[2642.06 --> 2642.82] are very excited.
[2643.42 --> 2643.50] Well,
[2643.56 --> 2644.08] and it's really how
[2644.08 --> 2644.86] it always should have been.
[2644.86 --> 2645.68] It is,
[2645.80 --> 2646.86] it does make sense.
[2647.00 --> 2647.64] So for me,
[2648.04 --> 2648.78] Docker Compose
[2648.78 --> 2649.58] was what made it click.
[2650.40 --> 2651.94] Because a simpleton
[2651.94 --> 2652.72] like myself
[2652.72 --> 2654.82] now has directories
[2654.82 --> 2655.70] that are backupable
[2655.70 --> 2657.00] that are just
[2657.00 --> 2658.48] loaded with YAML files
[2658.48 --> 2659.70] that just describe
[2659.70 --> 2660.44] my infrastructure.
[2661.76 --> 2662.84] And that's it
[2662.84 --> 2663.80] right there, man.
[2663.98 --> 2664.16] Like,
[2664.42 --> 2665.60] as soon as I went like,
[2665.70 --> 2665.88] oh,
[2666.42 --> 2667.12] and you know
[2667.12 --> 2668.20] how damn handy it is
[2668.20 --> 2668.66] to be able to just
[2668.66 --> 2669.64] cat a file and say like,
[2669.70 --> 2670.32] where did I end up
[2670.32 --> 2670.58] mounting?
[2670.74 --> 2671.44] Oh, right.
[2671.76 --> 2672.96] That thing points over here
[2672.96 --> 2673.50] for storage.
[2673.50 --> 2674.02] Okay, well,
[2674.10 --> 2674.80] that's where I have to go
[2674.80 --> 2675.42] on the file system.
[2675.76 --> 2676.86] I do that crap
[2676.86 --> 2677.80] all the time.
[2678.22 --> 2678.90] So for me,
[2679.04 --> 2679.92] Docker Compose
[2679.92 --> 2681.50] was this massive upgrade.
[2682.26 --> 2683.22] It took my occasional
[2683.22 --> 2684.02] use to Docker
[2684.02 --> 2685.06] from like,
[2685.28 --> 2685.44] yeah,
[2685.46 --> 2685.90] every now and then
[2685.90 --> 2686.52] I'll fire something up
[2686.52 --> 2687.12] to check it out