angular-cn/.devcontainer
George Kalpakas ee25034a77 build: update the recommended `Dockerfile` for VSCode remote development (#41396)
This commit updates the recommended `Dockerfile` for VSCode remote
development to take into account recent changes in our dev workflow
(updated Node.js version, vendored yarn, modified CircleCI config).

It also adds a note in the CircleCI config to keep the recommended
`Dockerfile` up-to-date with the Node.js version used on CI.

PR Close #41396
2021-04-05 12:41:34 -07:00
..
README.md docs: fix misspelled word in VSCode Remote Development guide (#41376) 2021-04-01 12:02:02 -07:00
recommended-Dockerfile build: update the recommended `Dockerfile` for VSCode remote development (#41396) 2021-04-05 12:41:34 -07:00
recommended-devcontainer.json build: add recommended config files for VSCode remote development (#30450) 2019-05-20 10:13:53 -07:00

README.md

VSCode Remote Development - Developing inside a Container

This folder contains configuration files that can be used to opt into working on this repository in a Docker container via VSCode's Remote Development feature (see below).

Info on remote development and developing inside a container with VSCode:

Usage

Prerequisite: Install Docker on your local environment.

To get started, read and follow the instuctions in Developing inside a Container. The .devcontainer/ directory contains pre-configured devcontainer.json and Dockerfile files, which you can use to set up remote development with a docker container.

In a nutshell, you need to:

The .devcontainer/devcontainer.json and .devcontainer/Dockerfile files are ignored by git, so you can have your own local versions. We may occasionally update the template files (recommended-devcontainer.json, recommended-Dockerfile), in which case you will need to manually update your local copies (if desired).

You can update and commit the recommended config files (which people use as basis for their local configs), if you find that something is broken, out-of-date or can be improved.

Please, keep in mind that any changes you make will potentially be used by many people on different environments. Try to keep these config files cross-platform compatible and free of personal preferences.