Multiple Base Domains
MultiDocker can serve projects under several base domains at the same time — for
example coding9.test and client-a.test. The base domains are stored
space-separated in config.env as BASE_DOMAINS, and index 0 is the primary.
Manage base domains
Section titled “Manage base domains”mdocker config domain list # current base domainsmdocker config domain add client-a.test # append a base domainmdocker config domain remove client-a.test # remove onemdocker config domain primary client-a.test # move it to the front (make it primary)Each of these commands cascades automatically: the wildcard certificate is regenerated, the DNS resolver is updated, the edge stack is refreshed, and all registered projects are re-rendered so their routing stays consistent.
The primary domain matters
Section titled “The primary domain matters”The primary base domain (index 0) is what new projects default to when you don’t pass
--host at init, and it’s the domain used to
derive default hostnames like <name>.<primary>. Use config domain primary to
change which one leads.
Related
Section titled “Related”- Changing the Base Domain
- Hostnames & Routing
- CLI:
config - Concept: DNS & TLS
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.