text
stringlengths
9
408
[2687.12 --> 2687.82] to like,
[2687.96 --> 2688.72] this is how I deploy
[2688.72 --> 2689.34] things now.
[2689.58 --> 2690.50] Because that Docker
[2690.50 --> 2691.26] Compose file,
[2691.40 --> 2693.88] it is a plain text way
[2693.88 --> 2695.02] for me to just
[2695.02 --> 2695.80] visualize
[2695.80 --> 2697.16] how an application
[2697.16 --> 2698.50] is built
[2698.50 --> 2699.46] and what it uses.
[2699.46 --> 2700.74] and I love it.
[2700.82 --> 2701.74] And so I'm glad
[2701.74 --> 2702.42] to actually see it
[2702.42 --> 2703.22] become like an official
[2703.22 --> 2704.24] part of the main
[2704.24 --> 2705.02] Docker app actually
[2705.02 --> 2705.46] because it means
[2705.46 --> 2705.86] it's going to be
[2705.86 --> 2706.48] around forever
[2706.48 --> 2707.76] and you start
[2707.76 --> 2708.36] to see support
[2708.36 --> 2708.78] in things like
[2708.78 --> 2709.70] Podman for Docker
[2709.70 --> 2710.20] Compose.
[2710.46 --> 2711.08] So it's starting
[2711.08 --> 2711.72] to become more
[2711.72 --> 2712.42] than just a Docker
[2712.42 --> 2713.04] thing and I think
[2713.04 --> 2713.66] that's great too.
[2714.32 --> 2714.40] Now,
[2714.44 --> 2714.80] if you want to hear
[2714.80 --> 2715.34] more about that,
[2715.40 --> 2715.70] you can go to
[2715.70 --> 2717.00] linuxactionnews.com
[2717.00 --> 2718.06] slash 209
[2718.06 --> 2718.70] where Chris and Wes
[2718.70 --> 2719.44] break that down
[2719.44 --> 2720.20] in a bit more detail
[2720.20 --> 2720.74] for you.
[2721.62 --> 2722.84] I wrote a blog post
[2722.84 --> 2723.90] a little while ago
[2723.90 --> 2725.34] about how I can
[2725.34 --> 2727.46] manage monolithic
[2727.46 --> 2728.68] Docker Compose files.
[2728.68 --> 2729.74] So I'm the type
[2729.74 --> 2730.38] of guy that tends
[2730.38 --> 2731.70] to slam my 30
[2731.70 --> 2732.62] containers all
[2732.62 --> 2733.82] into one massive
[2733.82 --> 2734.26] file.
[2734.74 --> 2735.60] I know some people
[2735.60 --> 2736.96] have different
[2736.96 --> 2738.18] preferences when it
[2738.18 --> 2739.08] comes to managing
[2739.08 --> 2739.86] these things through
[2739.86 --> 2741.52] stacks and what
[2741.52 --> 2741.88] have you,
[2741.98 --> 2743.20] but I found a
[2743.20 --> 2743.96] feature that got
[2743.96 --> 2744.54] added to Docker
[2744.54 --> 2745.36] Compose,
[2745.54 --> 2746.38] I'm not quite sure
[2746.38 --> 2746.74] when,
[2747.32 --> 2748.24] called profiles
[2748.24 --> 2750.14] and in essence
[2750.14 --> 2751.92] this allows you to
[2751.92 --> 2752.74] address multiple
[2752.74 --> 2753.90] services within a
[2753.90 --> 2754.72] monolithic file
[2754.72 --> 2755.20] itself.
[2755.36 --> 2756.06] I can give each
[2756.06 --> 2757.12] container a specific
[2757.12 --> 2758.54] profile like a tag
[2758.54 --> 2759.26] in the YAML
[2759.26 --> 2760.82] of like test or
[2760.82 --> 2761.52] prod or something
[2761.52 --> 2763.32] like that and I
[2763.32 --> 2764.32] can address all of
[2764.32 --> 2765.28] my test containers
[2765.28 --> 2766.36] within one massive
[2766.36 --> 2768.08] file as if it were
[2768.08 --> 2768.88] part of just a
[2768.88 --> 2769.74] smaller stack.
[2770.16 --> 2770.90] Probably a limited
[2770.90 --> 2772.10] use if you're using
[2772.10 --> 2773.92] stacks and you know
[2773.92 --> 2775.26] what stacks do,
[2775.48 --> 2776.18] you create a
[2776.18 --> 2776.50] directory,
[2776.60 --> 2777.14] you put the YAML
[2777.14 --> 2778.00] file inside that
[2778.00 --> 2779.72] directory and each
[2779.72 --> 2781.74] Compose file is in
[2781.74 --> 2782.88] each directory is
[2782.88 --> 2783.68] what's called a
[2783.68 --> 2784.78] stack and Compose
[2784.78 --> 2785.42] will treat that as
[2785.42 --> 2786.08] like a separate
[2786.08 --> 2787.16] entity.