History

Oliver Gould 325bf7d917 ci: Verify the devcontainer configuration in CI (#7700 ) This change adds a _devcontainer_ CI workflow that only runs when the devcontainer config or rust-toolchain changes. It ensures that the devcontainer uses the same Rust toolchain as the repo, that the devcontainer dockerfiles builds successfully, and that the devcontainer config references a real, published image. Signed-off-by: Oliver Gould <ver@buoyant.io>		2022-01-27 13:31:23 -08:00
..
Dockerfile	ci: Verify the devcontainer configuration in CI (#7700 )	2022-01-27 13:31:23 -08:00
README.md	Add a devcontainer configuration (#7583 )	2022-01-11 14:38:18 -08:00
devcontainer.json	devcontainer: Use dev:v5 (#7657 )	2022-01-24 07:31:15 -08:00

README.md

devcontainer

This directory provides a devcontainer configuration that configures a reproducible development environment for this project.

Docker

This configuration currently uses the parent host's Docker daemon (rather than running a separate docker daemon within in the container). It creates devcontainers on the host network so it's easy to use k3d clusters hosted in the parent host's docker daemon.

Customizing

This configuration is supposed to provide a minimal setup without catering to any one developer's personal tastes. Devcontainers can be extended with per-user configuration.

To add your own extensions to the devcontainer, configure default extensions in your VS Code settings:

    "remote.containers.defaultExtensions": [
        "eamodio.gitlens",
        "GitHub.copilot",
        "GitHub.vscode-pull-request-github",
        "mutantdino.resourcemonitor",
        "stateful.edge"
    ],

Furthermore, you can configure a dotfiles repository to perform customizations with a configuration like:

    "dotfiles.repository": "https://github.com/olix0r/dotfiles.git",