Estimated — self-paced course, go at your own speed.

Dev Containers and pre-commit: beyond a single repo

This track assumes you can already write a devcontainer.json and a multi-hook .pre-commit-config.yaml unaided — that's the [Intermediate](/en/academy/devcontainers-precommit-intermediate) level (modules 01 and 02 for Dev Container architecture, module 03 for pre-commit hooks). Here, the scale changes: a single repo becomes several services, a single machine becomes an entire team, and the questions change shape — it's no longer 'how do I write this file' but 'what breaks at scale, and how do I prove it'. Several modules ask you to produce a decision memo or an audit before showing you a model answer — that's deliberate: judgment is trained by practicing it first.

Modules

1. 1Multi-service devcontainer with docker-composeMove from a single-image devcontainer.json to a multi-service environment (application + database) driven by docker-compose.
2. 2Decision memo: prebuilt image vs. build on demandMeasure your real build time, then decide and justify in writing whether your team should publish prebuilt devcontainer images.
3. 3CI mirror for pre-commit hooksTake the multi-hook .pre-commit-config.yaml from the Intermediate track and run it identically in GitHub Actions.
4. 4Supply-chain audit: pinned vs. mutable referencesAudit the references from modules 01 and 03 for pinning risk, then compare your diagnosis against what pre-commit.com actually documents.
5. 5Diagnosing devcontainer performanceA measure → hypothesize → test → verify method for diagnosing a devcontainer with slow I/O — and how to tell whether your environment is even affected.
6. 6Org-wide standardization strategyCapstone: write a strategy for propagating your Dev Container + pre-commit setup across many repos in an organization, with no ready-made answer to follow.