mirror of https://github.com/docker/docs.git
ENGDOCS-2083 (#19944)
This commit is contained in:
Allie Sadler
GitHub
parent
94df07fd97
commit
b50530bf47
|
|
@ -48,8 +48,6 @@ aliases:
|
|||
- /compose/completion/
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
Docker Compose is a tool for defining and running multi-container applications.
|
||||
It is the key to unlocking a streamlined and efficient development and deployment experience.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ description: Explainer on the ways to set, use and manage environment variables
|
|||
keywords: compose, orchestration, environment, env file
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
Use environment variables to pass configuration information to containers at runtime.
|
||||
|
||||
Environment variables are key-value pairs that contain data that can be used by processes running inside a Docker container. They are often used to configure application settings and other parameters that may vary between different environments, such as development, testing, and production.
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ title: Compose FAQs
|
|||
tags: [FAQ]
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
### What is the difference between `docker compose` and `docker-compose`
|
||||
|
||||
Version one of the Docker Compose command-line binary was first released in 2014. It was written in Python, and is invoked with `docker-compose`. Typically, Compose V1 projects include a top-level version element in the compose.yml file, with values ranging from 2.0 to 3.8, which refer to the specific file formats.
|
||||
|
|
|
|||
|
|
@ -12,8 +12,6 @@ aliases:
|
|||
- /compose/install/compose-desktop/
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
This page contains summary information about the available options for installing Docker Compose.
|
||||
|
||||
## Installation scenarios
|
||||
|
|
|
|||
|
|
@ -12,8 +12,6 @@ aliases:
|
|||
- /compose/compose-linux/
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
On this page you can find instructions on how to install the Compose plugin on Linux from the command line.
|
||||
|
||||
To install the Compose plugin on Linux, you can either:
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ aliases:
|
|||
- /compose/install/other
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
On this page you can find instructions on how to install Compose standalone on Linux or Windows Server, from the command line.
|
||||
|
||||
### On Linux
|
||||
|
|
|
|||
|
|
@ -6,8 +6,6 @@ aliases:
|
|||
- /compose/history/
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
This page provides:
|
||||
- A brief history of the development of the Docker Compose CLI
|
||||
- A clear explanation of the major versions and file formats that make up Compose V1 and Compose V2
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ keywords: compose, compose file, merge, extends, include, docker compose, -f fla
|
|||
title: Overview
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
This section contains information on the ways you can work with multiple Compose files.
|
||||
|
||||
Using multiple Compose files lets you customize a Compose application for different environments or workflows. This is useful for large applications that may use dozens of containers, with ownership distributed across multiple teams. For example, if your organization or team uses a monorepo, each team may have their own “local” Compose file to run a subset of the application. They then need to rely on other teams to provide a reference Compose file that defines the expected way to run their own subset. Complexity moves from the code in to the infrastructure and the configuration file.
|
||||
|
|
|
|||
|
|
@ -4,8 +4,6 @@ keywords: compose, orchestration, containers, production
|
|||
title: Use Compose in production
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
When you define your app with Compose in development, you can use this
|
||||
definition to run your application in different environments such as CI,
|
||||
staging, and production.
|
||||
|
|
|
|||
|
|
@ -6,8 +6,6 @@ aliases:
|
|||
- /compose/reference/overview/
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
This page provides usage information for the `docker compose` command.
|
||||
|
||||
## Command options overview and help
|
||||
|
|
|
|||
|
|
@ -8,8 +8,6 @@ aliases:
|
|||
- /release-notes/docker-compose/
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
For more detailed information, see the [release notes in the Compose repo](https://github.com/docker/compose/releases/).
|
||||
|
||||
## 2.27.0
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ title: Control startup and shutdown order in Compose
|
|||
notoc: true
|
||||
---
|
||||
|
||||
{{< include "compose-eol.md" >}}
|
||||
|
||||
You can control the order of service startup and shutdown with the
|
||||
[depends_on](compose-file/05-services.md#depends_on) attribute. Compose always starts and stops
|
||||
containers in dependency order, where dependencies are determined by
|
||||
|
|
|
|||
Loading…
Reference in New Issue