Laravel Vapor Brand Logo Path?

[dmason30]

• Laravel Version: 9.7.0
• Nova Version: 4.2.2
• PHP Version: 8.1.4

Description:

Locally this config loads the logo correctly:

'brand' => [
    'logo' => public_path('images/logo.svg') // Shows empty logo on deploy
    // 'logo' => realpath(__DIR__.'/../public/images/logo.svg') // Shows default Laravel Nova logo on deploy,

    'colors' => [
        // ...
    ],
],

However, when it is deployed with vapor the public directory does not exist and it is unable to read the file and we end up with a blank logo in the portal:

The svg is uploaded to s3 with cloudront? What is the recommended way to configure the logo when using vapor?

[crynobone]

You should be able to do the following:

https://twitter.com/MikeVILT/status/1514581480240029710

Also instead of passing string directly you could also opt for using Storage::get('path-to/cloudfront/file.svg') if possible.

[dmason30]

Indeed this approach worked for me. Thanks! Adding screenshot just incase tweet disappears for future viewers.

[Senexis]

As an alternative, you can move or copy the logo to the resources folder (eg resources/images/logo.svg), then simply do:

// config/nova.php
'logo' => realpath(__DIR__.'/../resources/images/logo.svg'),

This will work on Vapor just fine.

[dmason30]

Yeah this is what i ended up going with, meant to update it here 👍

resource_path also works:

// config/nova.php
'logo' => resource_path('images/logo.svg'),

[eugenefvdm]

Does it have to be an SVG file?

[dmason30]

Yes. The contents of the file is read an injected into the page.

[emilianotisato]

For anyone still struggling with this on nova 4.
What I did was create a custom asset (https://nova.laravel.com/docs/4.0/customization/assets.html#defining-assets)
And you override the AppLogo vue component. So you have it totally under your control.

[dotsoftwarenl]

For anyone still struggling with this on nova 4. What I did was create a custom asset (https://nova.laravel.com/docs/4.0/customization/assets.html#defining-assets) And you override the AppLogo vue component. So you have it totally under your control.

Hi, I am trying to reproduce this but it seems to not work. Did you edit something elsewhere that you did not mention here?