ENGDOCS-1188 (#16565)

This commit is contained in:
Allie Sadler 2023-01-20 09:42:49 +00:00 committed by GitHub
parent cbfd5a5900
commit af075fa227
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 14 additions and 5 deletions

View File

@ -0,0 +1,6 @@
> **Dev Environments is changing**
>
>Were working hard to make Dev Environments work even better for you and your teams. In the coming months, well be introducing a new vision for Dev Environments.
>
>In the mean time, it may take us longer to respond to requests for support.
{: .important}

View File

@ -5,6 +5,7 @@ title: Launch a dev environment
redirect_from:
- /desktop/dev-environments/create-compose-dev-env/
---
{% include dev-envs-changing.md %}
You can launch a dev environment from a:
- Git repository
@ -31,9 +32,7 @@ To get started with Dev Environments, you must also install the following tools
- [Visual Studio Code](https://code.visualstudio.com/){:target="_blank" rel="noopener" class="_"}
- [Visual Studio Code Remote Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers){:target="_blank" rel="noopener" class="_"}
> **Note**
>
> After Git is installed, restart Docker Desktop. Select **Quit Docker Desktop**, and then start it again.
After Git is installed, restart Docker Desktop. Select **Quit Docker Desktop**, and then start it again.
## Launch a dev environment from a Git repository

View File

@ -3,6 +3,7 @@ description: Set up a dev Environments
keywords: Dev Environments, share, docker dev, Docker Desktop
title: Use the docker dev CLI plugin
---
{% include dev-envs-changing.md %}
Use the new `docker dev` CLI plugin to get the full Dev Environments experience from the terminal in addition to the Dashboard.

View File

@ -3,6 +3,8 @@ description: Dev Environments
keywords: Dev Environments, share, local, Compose
title: Overview
---
{% include dev-envs-changing.md %}
> **Beta**
>
> The Dev Environments feature is currently in [Beta](../../release-lifecycle.md#beta). We recommend that you do not use this in production environments.
@ -20,7 +22,6 @@ You can use Dev Environments through the intuitive GUI in Docker Dashboard or st
>**Changes to Dev Environments with Docker Desktop 4.13**
>
>Docker has simplified how you configure your dev environment project. All you need to get started is a `compose-dev.yaml` file. If you have an existing project with a `.docker/` folder this is automatically migrated the next time you launch.
{: .important}
Dev Environments is powered by [Docker Compose](/compose/). This allows Dev Environments to take advantage of all the benefits and features of Compose whilst adding an intuitive GUI where you can launch environments with the click of a button.

View File

@ -3,6 +3,7 @@ description: Set up a dev Environments
keywords: Dev Environments, share, set up, Compose, Docker Desktop
title: Set up a dev environment
---
{% include dev-envs-changing.md %}
>**Changes to Dev Environments with Docker Desktop 4.13**
>
@ -10,7 +11,7 @@ title: Set up a dev environment
>
> If you are using `.docker/docker-compose.yaml`, we move it to `../compose-dev.yaml`.
>If you are using `.docker/config.json`, we create a `../compose-dev.yaml` file with a single service named "app”. It is configured to use the image or Dockerfile referenced in the JSON as a starting point.
{: .important}
To set up a dev environment, there are additional configuration steps to tell Docker Desktop how to build, start, and use the right image for your services.
Dev Environments use an `compose-dev.yaml` file located at the root of your project. This file allows you to define the image required for a dedicated service, the ports you'd like to expose, along with additional configuration options.

View File

@ -3,6 +3,7 @@ description: Dev Environments
keywords: Dev Environments, share, Docker Desktop
title: Distribute your dev environment
---
{% include dev-envs-changing.md %}
The `compose-dev.yaml` config file makes distributing your dev environment easy so everyone can access the same code and any dependencies.