5 Commits

Include renames

Author	SHA1	Message	Date
octoturge	52cc84650a	Re-declare hashicorp/http provider to unblock existing workspace state ... Removing the jetbrains module (previous commit) dropped the only thing in these templates that used the hashicorp/http provider (the module fetched IDE metadata via it internally). terraform init only installs providers the current config declares, but any workspace whose state still has resources from a template version that included the jetbrains module needs that provider available to reconcile/destroy those entries - without it, plan/apply fails with "Missing required provider ... hashicorp/http". Re-declaring it in required_providers (all 6 templates) unblocks those existing workspaces' next apply. Safe to remove again once every workspace has updated past the jetbrains-module version.	2026-08-26 15:47:25 +02:00
octoturge	0c53bb6554	Add gh/tea to the CLI wizard, drop the JetBrains module from all templates ... - cli-setup-wizard.sh (identical across all 6 templates): add GitHub CLI (gh, installed via the official apt repo) and Gitea CLI (tea, official binary release to ~/.local/bin) as two more opt-in install-then-login prompts, alongside the existing Copilot/Antigravity/Claude Code CLI entries. Same pattern: skip if already installed, ask before installing, attempt login, never hard-fail the wizard. - main.tf (all 6 templates): remove the `module "jetbrains"` block - not used, dropped per request. - README.md: update the "Layout" blurb and CLI setup wizard tool list to match.	2026-08-26 14:58:51 +02:00
octoturgeandClaude Sonnet 5	22429aa4e3	Make each Coder template self-contained (fix coder templates push failure) ... coder templates push -d templates/<env> only uploads that directory to the Coder server, so main.tf's file() references reaching outside it via ../../profile-templates and ../../scripts failed at push/apply time ("Invalid function argument ... this function works only with files that are distributed as part of the configuration source code"). Confirmed via an actual failed run of coder-templates.yml once the runner network fix let it get that far. Fix: duplicate profile.code-profile, cli-setup-wizard.sh, and install-skills.sh into each templates/<env>/ directory and drop the old shared scripts/ and profile-templates/ directories. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-23 16:52:12 +02:00
octoturgeandClaude Sonnet 5	f6c432d21d	Install Agent Skills into all 3 AI CLIs, and use Bun instead of npm ... Adds scripts/install-skills.sh: pulls this repo's extensions/ skill bundles (SKILL.md-format) at workspace startup and installs them into Claude Code (~/.claude/skills), GitHub Copilot CLI (~/.copilot/skills), and Antigravity CLI (~/.gemini/config/skills). Every env gets the common awesome-skills-plugin bundle; COBOL/3D/TTRPG additionally get their matching skill(s) from custom-specialty-plugin via a per-template SPECIALTY_SKILLS value. Each template also installs Bun via a coder_script and hooks ~/.bun/bin onto PATH in .bashrc (the bun.sh installer doesn't reliably do this in a scripted shell). The CLI setup wizard now uses `bun install -g` instead of `npm install -g` for GitHub Copilot CLI and Claude Code CLI. All six templates re-validated with terraform init/validate against the real coder-server container on octo-winsrv. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-15 11:41:09 +02:00
octoturgeandClaude Sonnet 5	1beaac6e4f	Split single-container Coder template into per-env templates ... The old root main.tf tried to switch dev profiles inside one shared container via a coder_parameter dropdown; the settings-application path looked for a *.json cache file that never existed (the cache was written as *.code-profile), so profile settings never actually applied, and VS Code extensions were copied from extensions/ (which turns out to be Claude Code plugin bundles, not real VS Code extension packages). Replace it with one independent Coder template per environment (templates/default, 3d-printing, cobol, python, ttrpg, web). Each reads its matching profile-templates/*.code-profile file at template-push time via file()/jsondecode(), feeds the extension ID list straight into the code-server module's `extensions` input, and writes the raw settings.json text via a coder_script - no runtime Gitea zip download needed anymore. Also add scripts/cli-setup-wizard.sh, hooked into every new interactive shell until completed, offering to install/log into GitHub Copilot CLI, Google Antigravity CLI, and Claude Code CLI. VS Code extensions are deliberately not asked about there since Terraform already handles them. All six templates verified with `terraform init`/`validate` against the real coder-server container on octo-winsrv. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-15 11:28:26 +02:00