Skip to content

fix(dev-k8s): resolve Dockerfile.dev from smartem-decisions, refresh devops skill#218

Open
vredchenko wants to merge 2 commits into
mainfrom
fix/dev-k8s-build-path-and-skill
Open

fix(dev-k8s): resolve Dockerfile.dev from smartem-decisions, refresh devops skill#218
vredchenko wants to merge 2 commits into
mainfrom
fix/dev-k8s-build-path-and-skill

Conversation

@vredchenko
Copy link
Copy Markdown
Collaborator

Summary

  • dev-k8s.sh ensure_local_image ran docker build -f Dockerfile.dev from smartem-devtools, but the file lives in smartem-decisions. The build failed on every fresh up and the workaround (pre-build manually) was undocumented.
  • Adds SMARTEM_DECISIONS_PATH (defaults to the conventional sibling checkout) so the script knows where to find Dockerfile.dev, and fails fast with an actionable message if the file is missing.
  • Brings the devops skill back in sync with reality: script path moved to smartem-devtools, in-cluster Keycloak is the primary local auth provider, docker-compose Keycloak is the FE-only fallback, and the container build command matches the image tag dev-k8s.sh expects.

Why

Triggered while bringing up the local dev stack to test the FE against a fresh DB dump. dev-k8s.sh up failed with:

ERROR: failed to solve: failed to read dockerfile: open Dockerfile.dev: no such file or directory

Worked around by building manually first, but the on-disk skill instructions still pointed at the old smartem-decisions/scripts/k8s/dev-k8s.sh path and made no mention of the in-cluster Keycloak.

Test plan

  • bash -n scripts/k8s/dev-k8s.sh passes
  • SMARTEM_DECISIONS_PATH resolves to the conventional sibling layout under repos/DiamondLightSource/
  • dev-k8s.sh up reaches "All pods are running" with a freshly built backend image
  • Verify on a layout where smartem-decisions is at a non-default path by setting SMARTEM_DECISIONS_PATH explicitly

…devops skill

dev-k8s.sh `ensure_local_image` invoked `docker build -f Dockerfile.dev` from
$PROJECT_ROOT (smartem-devtools), but Dockerfile.dev lives in smartem-decisions.
The build failed with "no such file or directory" on every fresh `up`, leaving
operators to discover the workaround themselves.

Introduce SMARTEM_DECISIONS_PATH, defaulting to a sibling checkout next to
smartem-devtools. Fail fast with a clear message when the file is missing so
non-standard layouts can be configured rather than silently broken.

Refresh the devops skill in the same change: the script path moved to
smartem-devtools, the dev stack now ships an in-cluster Keycloak (with the
docker-compose mock kept as the FE-only fallback), and the build command in
the skill's container section matches what dev-k8s.sh expects.
@vredchenko vredchenko added documentation Improvements or additions to project documentation bugfixing Fixing defects or unexpected behavior in existing code devops CI/CD, deployment, infrastructure, or tooling work labels May 28, 2026
@github-actions github-actions Bot added the smartem-devtools:claude Claude Code configuration, skills, and prompts label May 28, 2026
Language-less ASCII-art fences (diagrams, terminal output, plain text) were
being heuristically tokenised by shiki/rehype-pretty-code, producing stripey
per-line backgrounds and broken alignment because the highlighter guessed at
keywords that were not there.

Set rehype-pretty-code's `defaultLang: 'text'` so any fenced block without an
explicit language renders as a uniform monospace block. Source markdown stays
unchanged — no doc-side annotations needed.

Verified locally against docs/agent/authentication.md: the client_credentials
diagram now renders as a single contiguous block.

See also #219 (view-source link on docs pages) and #220 (rewrite relative .md
links in webui rendering).
@github-actions github-actions Bot added the smartem-devtools:webui Developer dashboard web interface label May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfixing Fixing defects or unexpected behavior in existing code devops CI/CD, deployment, infrastructure, or tooling work documentation Improvements or additions to project documentation smartem-devtools:claude Claude Code configuration, skills, and prompts smartem-devtools:webui Developer dashboard web interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant