SAService Architect Back to designer
SAService ArchitectDocumentation
Code GenerationDocker and local infrastructure
Code generation Nexus + Git mirror

Dependency cache

The generated cache makes repeated builds reproducible and reduces public-registry traffic across language ecosystems.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

Behavior

  • Nexus proxies Go, npm, PyPI, Cargo, Helm, Maven, APT and Docker registries used by generated workspaces.
  • A separate Git mirror caches source repositories.
  • Host and Docker Desktop builds receive different generated endpoint environments.
  • Stopping preserves artifacts; cleaning removes them.

Dependency cache commands

Complete generated cache command surface.

CommandScopeDescription
make dependency-cache-upWorkspace

Start and configure the shared Nexus package proxy and Git mirror.

make dependency-cache-statusWorkspace

Show proxy and mirror health.

make dependency-cache-refreshWorkspace

Refresh cached Git mirrors from their upstream repositories.

make dependency-cache-envWorkspace

Print package-manager environment variables for host commands.

make dependency-cache-docker-envWorkspace

Print equivalent proxy settings reachable from Docker Desktop builds.

make dependency-cache-docker-buildWorkspace

Start the cache and build all images through it.

make dependency-cache-downWorkspace

Stop cache services but preserve downloaded artifacts.

make dependency-cache-cleanWorkspace

Stop cache services and remove all cached artifacts.

make dependency-source-cache-invalidateWorkspace

Recreate C++ source/CMake state while retaining ccache and Nexus data.

Cached image build

make dependency-cache-up
eval "$(make dependency-cache-env)"
make dependency-cache-docker-build
make dependency-cache-status
make dependency-cache-down