Make config multi-site aware?

[janhenckens]

Is your feature request related to a problem? Please describe.
When we're adding a new site to a existing project, we would like to enable Marker.io for that new site but not for the others - frontend wise.

Describe the solution you'd like
For the project and the enableWidgetFe, it would be useful if we could have craft-style site settings, where each config option can contain an array with site handles.

Additional context
This can't work for the CP, where if enabled it will always be visible, that's ok for our case.

[mike-moreau]

@janhenckens that's a good idea. We'll keep it in mind for future updates, but I could not guarantee if it is something we'll be adding.

In the short term, could some PHP in your config file meet the need? (This is untested)

<?php

use Craft;
use craft\web\Application;

/** @var Application $app */
$app = Craft::$app;

$handle = $app->getSites()->getCurrentSite()->handle;

$projectLUT = [
    'targetSite' => 'abc123',
    'staging' => 'def456',
];

return [
    '*' => [
        'project' => $projectLUT[$handle] ?? '',
        'enableWidgetFe' => in_array($handle, ['targetSite', 'staging']),
        'enableWidgetCp' => false,
        'requireLogin' => false,
        'silent' => false,
        'renderDelay' => 1200,
        'keyboardShortcuts' => false,
        'useNativeScreenshot' => false,
        'extension' => false,
    ],
    'staging' => [
        'enableWidgetFe' => true,
        // 'enableWidgetCp' => false,
    ]
];

[mike-moreau]

This would be in config/markerio.php

[janhenckens]

Thanks @mike-moreau! Happy to make a PR for this if you like.

[mike-moreau]

Sure thing!

[janhenckens]

Which branch are you starting from @mike-moreau (I see Craft 5 and main)?

[mike-moreau]

@janhenckens main 👍