From 34afce6f6c722c7b5dfea72c4cc1111c9147be22 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 29 Oct 2026 12:04:19 +0000 Subject: [PATCH] docs: list the dev container profiles on the local setup page (Gameplane spec 026 T033) Co-Authored-By: Claude Opus 5.5 Signed-off-by: Claude --- src/content/docs/local-development-setup.mdx | 26 ++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/src/content/docs/local-development-setup.mdx b/src/content/docs/local-development-setup.mdx index 78f2c42..71bf0d5 100644 --- a/src/content/docs/local-development-setup.mdx +++ b/src/content/docs/local-development-setup.mdx @@ -67,6 +67,32 @@ The Make targets create local infrastructure, build and load images, push module ]} /> +## Dev containers + +The repository ships one dev container profile per area, so a container installs only what your change needs. Pick it in VS Code with "Dev Containers: Reopen in Container", or under "Dev container configuration" in Codespaces; the full profile is the default. + + + +The [profile table in docs/contributing.md](https://github.com/GameplanePanel/Gameplane/blob/master/docs/contributing.md#dev-container-profiles) lists what each profile installs, its setup time, and when to use it. A Make target that needs a missing tool stops with a `need:` message naming the profile to reopen in. + ## Debug the environment Keep host and cluster registry addresses, kube context, namespaces, image tags, and Helm values aligned.