Files
coder/dogfood/coder-envbuilder/README.md
T
Cian Johnston 09dd69a7e8 chore(dogfood): include multiple templates under dogfood/ (#16846)
* Renames `dogfood/contents` to `dogfood/coder`.
* Moves `coder-envbuilder` to `dogfood/coder-envbuilder`.
* Updates `dogfood/main.tf` to push `coder-envbuilder` template.
* Replaces hard-coded organization IDs with
`data.coderd_organization.default.id`.
2025-03-11 13:17:40 +00:00

16 lines
910 B
Markdown

# envbuilder dogfood template
This template uses the same image as the [dogfood](../dogfood) template, but
builds it on-demand using the latest _preview_ version of [envbuilder](https://github.com/coder/envbuilder).
In theory, it should work with any Git repository containing a `devcontainer.json`.
The Git repository specified by `devcontainer_repo` is cloned into `/workspaces` upon startup and the container is built from the devcontainer located under the path specified by `devcontainer_dir`.
The `region` parameters are the same as for the [dogfood](../dogfood) template.
The `/workspaces` directory is persisted as a Docker volume, so any changes you make to the dogfood Dockerfile or devcontainer.json will be applied upon restarting your workspace.
## Personalization
The startup script runs your `~/personalize` file if it exists.
You also have a persistent home directory under `/home/coder`.