I have added the following line to post-init-settings.php
$wgLogos = [ '1x' => "$wgScriptPath/images/LetterDLogo.png" ];
when I look at the resulting source I see this:
<a id="nb-logo" href="[/wiki/Main_Page](https://wiki.mydomain.com/wiki/Main_Page)" title="Main Page" class="mx-4 mw-wiki-logo" style="background-image: url(/w/images/LetterDLogo.png);" role="link" tabindex="0" aria-label="My Site logo - Return to Main Page"></a>
</div>
The file is located in /app/bluespice/w/images
It does not load. I’m not sure what to put into the config file to get this logo to brand my site.
Hello Ryan,
the parameter $wgLogos is defining a URL of the image, meaning that it wants to visit file https://wiki.mydomain.com/w/images/LetterDLogo.png directly, which is actually not quite safe (hence disallowed by the nginx inside web container).
post-init-settings.php is a nice place for such a line. For example if I upload my example logo pic ghunicorn.png on page Special:Upload and check its permanent relative link /w/nsfr_img_auth.php/7/7d/ghunicorn.png, I can set the following line
$wgLogos = [ '1x' => "/w/nsfr_img_auth.php/7/7d/ghunicorn.png" ];
Even easier, extension FlexiSkin is integrated into BlueSpice. You can easily customize your main logo, favicon, colors and many other global styles on page Special:FlexiSkin.
One further hint on the image directory: instead of putting the images inside the /app/bluespice/w/images, the persistent data storage directory on the host machine is mapped into the container. You can find your images in <data-dir-set-in-.env>/wiki/bluespice/images in the host machine, which is mapped to /data/bluespice/images inside the web and the task containers.
Fantastic. Using the Skins link to access FlexiSkin worked!