Coder workspace templates for code.bert133.dev
https://code.bert133.dev
- HCL 89.5%
- Dockerfile 10.5%
- Adds GitLens, EmojiSense, Markdown All in One, and markdownlint to the code-server extension list for both templates. - Sets chat.agent.enabled=false in the shared baseline settings so the chat agent UI stays off alongside Copilot and the chat command center. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| frc-2026 | ||
| frc-2027 | ||
| shared | ||
| .gitignore | ||
| README.md | ||
bert/coder-templates
Terraform workspace templates for the BERT 133 Coder deployment.
A Forgejo Actions workflow (.forgejo/workflows/push-templates.yaml) runs on
every push to main and reconciles the templates in this repo into the
in-cluster Coder at https://code.bert133.dev via
coder templates push.
This is the only path by which template state reaches Coder — no mentor pushes
templates from a laptop. The workflow authenticates as the bert-ci Coder
user (Template Admin) via a long-lived token held in the CODER_SESSION_TOKEN
Forgejo Actions secret on this repo.
See the design plan in the bert/server repo:
docs/design-plans/2026-04-21-workspaces.md.
Workflow jobs
push-templates.yaml runs two jobs on every push to main:
build-images— for each template with aDockerfile, builds and pushes a custom workspace image to the Forgejo container registry atforge.bert133.dev/bert/<template>:{latest,<sha>}. Authenticates with the auto-injectedGITHUB_TOKEN(Forgejo grants workflow runswrite:packagescope for the owning org).push-templates— reconciles Terraform templates into Coder viacoder templates push. Runs afterbuild-imagesso templateimage =references always point at an already-pushed tag.
Adding a template
- Create a new top-level directory (e.g.
frc-2028/). - Add a
Dockerfile(optional — only if you need a custom image) and amain.tfdeclaring thecoder/coderprovider,coder_workspacedata source, andcoder_agentresource. If the template uses a custom image, also add the template name to thematrix.templatelist in.forgejo/workflows/push-templates.yaml. - Commit, push to a feature branch, open a PR.
- On merge to
main, the workflow builds the image (if present) and then pushes every template. Coder hashes template contents and skips unchanged ones.
Templates
frc-2026/— FRC 2026 season (roboRIO, JDK 17, WPILib extension v2026.2.1). Current-season stable stack.frc-2027/— FRC 2027 season (systemcore, JDK 25, WPILib extension v2027.0.0-alpha-2). Pre-release; expect rough edges.