Artisan error: A facade root has not been set

[akbariandev]

Scribe version

5.2.1

PHP version

8.4.8

Laravel version

12.13.0

Scribe config

type => "external_laravel"
theme => "scalar"
laravel.docs_url => "/api/documentation"

What happened?

I used scribe on my local project (Windows) and it works well. But when I push it on my server (Ubuntu 24) it prevent to run any composer or artisan command and every time I will give below error:

@php artisan package:discover --ansi
PHP Fatal error:  Uncaught RuntimeException: A facade root has not been set. in /vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:358

Consider I can't stop the error until I remoove the /config/scribe.php.

Docs

• I've checked the docs, the troubleshooting guide, and existing issues, but I didn't find a solution

[LucianMihalache]

@akbariandev can you run php artisan package:discover -vvv for more details?
Also, try to rerun composer commands, including dump-autoload.

[akbariandev]

Thanks @LucianMihalache
Both commands lead to same error that I mentioned. It prevents to run any artisan or composer command until removing scribe.php. Isn't that strange? 🤕

[LucianMihalache]

@akbariandev that's very weird because I just installed scribe on a fresh laravel and I had no issues.
You're saying that if you remove /config/scribe.php it works
Are you sure that's all you've changed in there?

[akbariandev]

@LucianMihalache
I rollback whole changes made by scribe using git. But I saw this single file never removed in rollback process (I tested multiple times) and this single file prevent to use any composer or artisan commands (as I mentioned before) so every thing stopped.
Let me know that should I call these below commands also on my VPS. Actually I just ran it on my local to generate files and then pushed it on VPS

php artisan vendor:publish --provider="Knuckles\Scribe\ScribeServiceProvider"
php artisan scribe:generate

[LucianMihalache]

@akbariandev
So if you removed scribe, but you left the /config/scribe.php in there, of course it won't work, because scribe.php has its own Facade calls in it like Defaults, Strategies\StaticData, etc
So on your VPS, after you pull the code, don't forget to also run composer install so it grabs scribe from composer.json

[akbariandev]

@LucianMihalache . After pull, no composer command works. So it prevents to install scribe package. The .scribe folder, scribe.php and resources files + changes of composer.json and composer.lock pushed on my VPS and when I try to run artisan discover or composer install (to install scribe package) the error will occur.

[LucianMihalache]

Are you using a default laravel? Because laravel should not care about /config/* stuff when it does composer install
Try to install scribe before adding the rest of the things.

[akbariandev]

I don't understand the meaning of default Laravel, but I will try to install scribe before adding files