profile
mdocker profile manages the override templates applied to projects. See
Writing & Customizing Profiles for the workflow and
Profiles & Templating for the concept.
profile list
Section titled “profile list”List known profile templates (read-only).
mdocker profile listmdocker profile list --jsonprofile show
Section titled “profile show”Print the effective YAML — the user override if present, otherwise the bundled
default. --default forces the bundle / generic-starter.
mdocker profile show <name>mdocker profile show <name> --defaultprofile path
Section titled “profile path”Print the effective template path (read-only).
mdocker profile path <name>profile validate
Section titled “profile validate”Check yq syntax and placeholders. The JSON form also lists placeholders[].
Exits 1 if invalid.
mdocker profile validate <name>cat my.yml | mdocker profile validate --stdin --jsonprofile save
Section titled “profile save”Write a user override from stdin (validated unless --force).
cat my.yml | mdocker profile save <name>cat my.yml | mdocker profile save <name> --forceSaved to ~/.config/multi-docker/profiles/<name>.yml.
profile reset
Section titled “profile reset”Delete the user override (back to the bundled default). --purge allows deleting a
custom-only profile.
mdocker profile reset <name>mdocker profile reset <name> --purgeprofile rerender-affected
Section titled “profile rerender-affected”Re-render every registered project using this profile. Prints a JSON array of the re-rendered project names.
mdocker profile rerender-affected <name>Related
Section titled “Related”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.