mirror of
https://github.com/coder/coder.git
synced 2026-06-04 13:38:21 +00:00
Mathias Fredriksson
97bc7eb9e5
Dev container admin docs were scattered across two locations: the Docker-based
integration under extending-templates/ and Envbuilder under managing-templates/.
There was no landing page explaining that two approaches exist or helping admins
choose between them.
This moves everything under admin/integrations/devcontainers/ with a decision
guide at the top. Dev containers are an integration with the dev container
specification, so integrations/ is a natural fit alongside JFrog, Vault, etc.
Stub pages remain at the original locations for discoverability.
New structure:
admin/integrations/devcontainers/
├── index.md # Landing page + decision guide
├── integration.md # Docker-based dev containers
└── envbuilder/
├── index.md
├── add-envbuilder.md
├── envbuilder-security-caching.md
└── envbuilder-releases-known-issues.md
Refs #21080
15 lines
606 B
Markdown
15 lines
606 B
Markdown
# Envbuilder
|
|
|
|
Envbuilder shifts environment definition from template administrators to
|
|
developers. Instead of baking tools into template images, developers define
|
|
their environments via `devcontainer.json` files in their repositories.
|
|
|
|
Envbuilder transforms the workspace image itself from a dev container
|
|
configuration, without requiring a Docker daemon.
|
|
|
|
For setup instructions, see
|
|
[Envbuilder documentation](../../integrations/devcontainers/envbuilder/index.md).
|
|
|
|
For an alternative that uses Docker inside workspaces, see
|
|
[Dev Containers Integration](../../integrations/devcontainers/integration.md).
|