Turning off a site in multi-site/multi-environment config Given a multi site setup (domain1.com, domain2.com) that also uses multiple environments (dev, staging, production) - how would one configure one of the sites to be turned off in the production environment?

I'm currently trying the following.

return [
    // Global settings
    '*' =&gt; [
        // removed for clarity
    ],


    'dev' =&gt; [
        'devMode' =&gt; true,
        'isSystemLive' =&gt; [
            'domain1.com' =&gt; true,
            'domain2.com' =&gt; false
        ]
    ],

    // Staging environment settings
    'staging' =&gt; [
        'devMode' =&gt; true,
        'isSystemLive' =&gt; [
            'domain1.com' =&gt; true,
            'domain2.com' =&gt; false
        ]
    ],

    // Production environment settings
    'production' =&gt; [
        'devMode' =&gt; false,
        'isSystemLive' =&gt; [
            'domain1.com' =&gt; true,
            'domain2.com' =&gt; false
        ]
    ]
];


Which I would have expected to have domain2.com turned off but domain1.com remains on. However, both sites are on.

I have also tried rearranging the config using the following structure (stripped back for brevity) 

return [
    'domain1.com' =&gt; [
        '*' =&gt; [
            // default for domain1
        ],

        'dev' =&gt; [
            'isSystemLive' =&gt; true
        ],

        'staging' =&gt; [
            'isSystemLive' =&gt; true
        ],

        'production' =&gt; [
            'isSystemLive' =&gt; true
        ]
    ],

    'domain2.com' =&gt; [
        '*' =&gt; [
            // default for domain2
        ],

        'dev' =&gt; [
            'isSystemLive' =&gt; false
        ],

        'staging' =&gt; [
            'isSystemLive' =&gt; false
        ],

        'production' =&gt; [
            'isSystemLive' =&gt; false
        ]
    ],
]


But this also doesn't work.

So how should I specify different multi-environment configs for each site?
The isSystemLive config setting isn't multi-site aware. It sets the entire Craft installation on or off, rather than per site, so you'll need to find a different method to disable domain2.com on the production server.

Untested, but you could try to set the baseUrl for domain2.com to an empty string on production and see if that works.