Setting up a Blaze development environment currently means installing the whole toolchain by hand: a Temurin JDK, the Clojure CLI, clj-kondo, cljfmt, Node.js, actionlint, ShellCheck and dashboard-linter, each in the version CI uses (see DEVELOPMENT.md).
A Dev Container configuration would make that reproducible: a contributor opens the repository in an IDE supporting the spec and gets an environment in which make fmt, make lint, make test and the module REPLs work out of the box, with the tool versions pinned to the ones in .github/workflows/build.yml.
Target environments:
- IntelliJ IDEA (Dev Containers support, Cursive for Clojure)
- Claude Code, running inside the container
Scope:
.devcontainer/devcontainer.json and a Dockerfile based on Ubuntu 24.04 (matching ubuntu-24.04 in CI), installing the tools with pinned versions and checksums, annotated for Renovate- a post-create step that prepares the workspace (
make build-ig, make prep)
- persistent caches for
~/.m2 and ~/.gitlibs so dependencies survive container rebuilds
- documentation in
DEVELOPMENT.md
Out of scope: Docker access from inside the container. Building the Blaze image (make build-image) and the docker compose based integration tests under .github/ stay on the host.
Setting up a Blaze development environment currently means installing the whole toolchain by hand: a Temurin JDK, the Clojure CLI, clj-kondo, cljfmt, Node.js, actionlint, ShellCheck and dashboard-linter, each in the version CI uses (see
DEVELOPMENT.md).A Dev Container configuration would make that reproducible: a contributor opens the repository in an IDE supporting the spec and gets an environment in which
make fmt,make lint,make testand the module REPLs work out of the box, with the tool versions pinned to the ones in.github/workflows/build.yml.Target environments:
Scope:
.devcontainer/devcontainer.jsonand aDockerfilebased on Ubuntu 24.04 (matchingubuntu-24.04in CI), installing the tools with pinned versions and checksums, annotated for Renovatemake build-ig,make prep)~/.m2and~/.gitlibsso dependencies survive container rebuildsDEVELOPMENT.mdOut of scope: Docker access from inside the container. Building the Blaze image (
make build-image) and the docker compose based integration tests under.github/stay on the host.