Enabling debugbar in production environment is impossible

[JacekAndrzejewski]

I've been using debugbar in the production environment behind a cookie and an auth check for quite some time.
However after upgrading to v4 I noticed it no longer works.

I tried to enable it by setting config debugbar.enabled to true, yet that didn't help.

I found out that early return in ServiceProvider->boot() ignores all the config options and is fully dependent on APP_DEBUG and APP_ENV.

laravel-debugbar/src/ServiceProvider.php

Lines 63 to 66 in e00daff

	// Eearly return if debugbar can not enabled
	if (!LaravelDebugbar::canBeEnabled()) {
	return;
	}

Another place that ignores the config the same way is LaravelDebugbar->isEnabled()

laravel-debugbar/src/LaravelDebugbar.php

Lines 564 to 566 in e00daff

	if (!static::canBeEnabled()) {
	$this->enabled = false;
	} else {

As a temporary workaround I applied a composer patch for both of those places to check the value of config('debugbar.enabled').
That's a dirty fix, but it's good enough for my purposes, and from testing I see only users passing the auth gate have access. Debugbar also turns off early in the stack if someone doesn't pass the gate (thanks to a middleware), so performance impact is negligible.

I could provide a PR, but I feel that there might be a better solution I don't see.

Workaround:

Adding patch files in composer.json for use with cweagans/composer-patches

"extra": {
        "patches": {
            "fruitcake/laravel-debugbar": {
                "Fix debugbar boot to allow running on production": "patches/debugbar_service_provider.patch",
                "Fix debugbar isEnabled to allow running on production": "patches/debugbar_is_enabled.patch"
            }
        }
    },

patches/debugbar_service_provider.patch

--- src/ServiceProvider.php
+++ src/ServiceProvider.php
@@ -58,7 +58,7 @@
         }

         // Eearly return if debugbar can not enabled
-        if (!LaravelDebugbar::canBeEnabled()) {
+        if (!LaravelDebugbar::canBeEnabled() && !config('debugbar.enabled', false)) {
             return;
         }

patches/debugbar_is_enabled.patch

--- src/LaravelDebugbar.php
+++ src/LaravelDebugbar.php
@@ -561,7 +561,7 @@
     public function isEnabled(): bool
     {
         if ($this->enabled === null) {
-            if (!static::canBeEnabled()) {
+            if (!static::canBeEnabled() && !config('debugbar.enabled', false)) {
                 $this->enabled = false;
             } else {
                 $configEnabled = value(config('debugbar.enabled'));

[erikn69]

• Tweak boot check #1991 (comment)

that thread could helps you

if(Auth::user()->hasRole('Super Admin')){
   $this->app['env'] = 'local';
   config(['debugbar.enabled' => true, 'debugbar.storage.open' => true, 'app.debug' => true]);
   $this->app->register(new \Fruitcake\LaravelDebugbar\ServiceProvider($this->app));
}

[barryvdh]

Hmm yeah I think I should do something like override the debugbar check.

[bsienn-khan]

It's reasonable and required for as a developer user to be able to use the debugbar even in production environment.
Previously i was able to to middleware with Debugbar::enable();

[barryvdh]

I created a PR in #2026

[barryvdh]

Please test on dev-master or 4.2.x@dev, then I can tag it

[JacekAndrzejewski]

Please test on dev-master or 4.2.x@dev, then I can tag it

Tested, works the same as my patch.
When I set DEBUGBAR_FORCE_ALLOW_ENABLE=true then I can call Debugbar::enable(); in middleware for users with permissions and debugbar is then visible.