Your First Project
The Quickstart gets you running fast. This page runs the same commands but explains what each one does, so you understand the machinery before you rely on it.
-
Register the project — and watch the profile detection.
mdocker init mdocker init ~/Projects/aurorainitreads the project’s compose file and runs a profile heuristic (engine/detect.sh) that looks at image and service names to choose a template — for exampleshopware-dockware,strapi-next,api-web-postgres, or thegenericfallback. It then generates~/.config/multi-docker/overrides/<name>.override.ymland records the project inregistry.json.You can override the guesses:
explicit name, profile and host mdocker init ~/Projects/aurora \--name aurora \--profile generic \--host aurora.coding9.testSee Registering & Detecting Projects for the full set of options.
-
Start the project — and understand the port pre-flight.
mdocker up mdocker up auroraBefore starting,
upruns a port-conflict pre-flight. If a host port your project would publish is already taken by a foreign process, MultiDocker finds a free replacement, persists it underport_overridesin the registry and writes a<name>.ports.yml. Then it renders theCOMPOSE_FILEchain and callsdocker compose up -d. The containers join themulti-docker-edgenetwork and Traefik starts routing immediately. -
Open it — trusted HTTPS, no warnings.
mdocker open mdocker open auroraThe hostname resolves because
dnsmasqanswers*.coding9.testwith127.0.0.1and the macOS resolver forwards that domain to it. The mkcert wildcard certificate makes the TLS connection trusted, so the browser shows a padlock rather than a security warning. -
Inspect what is running.
mdocker inspect mdocker inspect aurorainspectlists each service’s container, ports and environment, plus a ready-to-copy connection string (mysql://,postgres://, …). Add--jsonfor scripting.
Where to go next
Section titled “Where to go next”- Manage hostnames and routing: Hostnames & Routing.
- Reach the database from your host: Accessing Databases.
- Understand the internals: Architecture Overview.
Cookie settings
We only use statistics tools if you allow it. Necessary storage keeps this site working; everything else is off until you decide.
Stores your choice from this dialog in your browser (localStorage). No cookie, no transfer to third parties.
Google Analytics 4 via Google Tag Manager, to measure how the site is used. Loaded only after you allow it.