菜单
Push an updated Coder workspace Terraform template and redeploy running workspaces onto it. Use when workspace-template/main.tf changes (resources, volumes, etc.) need to reach live Coder workspaces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit CloudNativePG (CNPG) clusters for backup health, S3 storage bloat, and disk-space risk — schedule misconfiguration, WAL/archive_timeout churn, orphaned backups, compression, and PVC resize status. Use when investigating CNPG backup storage growth, a "storage near empty" alert on the backup target (e.g. QNAP), a crash-looping/"Not enough disk space" CNPG cluster, or doing a periodic CNPG health check.
Diagnose and fix ONLYOFFICE Document Server showing "An error has occurred while opening the file" with no failed requests visible in the browser. Root cause is usually an orphaned task_result row in the docserver's Postgres DB, left over from a conversion interrupted by a pod crash/OOM/restart.
Task commands, bootstrap sequence, CI/CD, branch/PR workflow, linting, and devcontainer setup for the home-ops repository.
Use when auditing disk health, filesystem usage, or I/O on cluster nodes — especially when filesystem queries return incomplete results or a node's second drive is missing from metrics.
Use when removing, replacing, or decommissioning a Talos node — covers the correct talosctl reset workflow
Reference for cluster infrastructure components, Talos configuration, network topology, and auto-managed files. Use when querying component roles, versions, IPs, or understanding what files must not be manually edited.
| name | coder-workspace-template-deploy |
| description | Push an updated Coder workspace Terraform template and redeploy running workspaces onto it. Use when workspace-template/main.tf changes (resources, volumes, etc.) need to reach live Coder workspaces. |
| user-invocable | false |
| origin | auto-extracted |
Extracted: 2026-07-07
Context: Editing cluster/apps/ai/coder/workspace-template/main.tf and needing the change (e.g. resource requests/limits) to actually reach the running workspaces.
Committing a change to workspace-template/main.tf has zero effect on already-running Coder workspaces. The template must be pushed to the Coder server as a new version, and each workspace must be individually rebuilt onto that version.
Check CLI/server version match. coder whoami prints a "version mismatch" warning (with the exact required version) if the local coder CLI is behind the server — commands still run, but reinstall to match and avoid edge-case failures:
ARCH=$(dpkg --print-architecture)
curl -sL "https://github.com/coder/coder/releases/download/<VERSION>/coder_<version-no-v>_linux_${ARCH}.tar.gz" \
| tar -xzO ./coder | sudo tee /usr/bin/coder > /dev/null
sudo chmod +x /usr/bin/coder
Note the extracted path is ./coder, not coder — the tarball stores it with a leading ./.
Push the new template version:
cd cluster/apps/ai/coder/workspace-template
coder templates push sandbox --directory . -y
The live template is named sandbox (the original design doc called it sandbox-workspace — that name was never actually used).
Redeploy each running workspace with coder update <owner>/<workspace> — not coder restart, which keeps the workspace on its old template version. update has no -y/--yes flag (unlike create), but it does not prompt interactively as long as no parameter values changed, so it completes non-interactively in that case.
Run updates one at a time, not looped with combined output capture. Each update does a full stop → plan → apply → start cycle (roughly 30–90s). Piping several sequential coder update calls into one shell command easily exceeds a 2-minute tool timeout across multiple workspaces — invoke each as its own command instead.
Verify:
coder list
Confirm STATUS is Started, HEALTHY is true, and OUTDATED is false for every workspace.
After merging any change to cluster/apps/ai/coder/workspace-template/main.tf that should apply to already-running workspaces.