Part of the workspace-wide standards rollout. Establishes where work lives (issues vs ADRs vs standing law), scaffolds `docs/agents/` for the engineering skills, and adopts ADR-0001 locally. See `sow-platform` ADR-0021 for the `sow-docs` retirement.Reviewed-on: #51 Reviewed-by: xtul <mpiasecki720@protonmail.com> Co-authored-by: vickydotbat <vickydotbat@tutamail.com>
1.4 KiB
ADR-0004: Nix-built OCI images start server-side with Crucible; local Anvil images deferred
-
Status: Accepted
-
Date: 2026-06-12
-
Migrated from:
sow-docs07-decisions-log.mdentry D29, on the retirement ofsow-docs. Content is the original decision, unchanged. -
Decision: Introduce Nix-built OCI images as an artifact-production option, starting with
sow-tools/Crucible in server-side CI.sow-toolswill grow a Nix-builtcruciblepackage pluscrucible-image; PR CI builds/smokes it andmainpublishes the normal pinned OCI imageregistry.westgate.pw/deployment/crucible:<sha>.docker/Dockerfilestays during parity and as the client-compatible fallback. -
Local rule: Nix users may get optional wrappers that provide tools and call the existing Dockerfiles for local Anvil/NWServer testing. A true
nix build .#nwserver-test-imageis explicitly deferred until realsow-codebase/srcexists and the Dockerfile image is proven. -
Rationale: Server-side image build shape is harder to change once deploy promotion and registry gates are active, so prove Nix image builds before cutover. Crucible is the lowest-risk pilot because it is a Go toolchain image; NodeBB and Anvil/NWServer depend more heavily on upstream container filesystem semantics.
-
Non-goals: no source builds in
sow-platform; nonix-sidecaror Kubernetes-style runtime cache layer; no removal of client Dockerfiles.