Skip to content

chore: add envbuilder-dogfood template #13720

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 28, 2024
Merged

chore: add envbuilder-dogfood template #13720

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e69cbb1
chore: add envbuilder-dogfood template
johnstcn Jun 28, 2024
a5bdbfe
make fmt
johnstcn Jun 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions envbuilder-dogfood/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# 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`.
Loading
Loading