---
title: 'Inspect Laravel config and service container bindings'
description: 'Use Tinker to read config values, resolve services, and confirm runtime bindings without adding temporary routes or debug controllers.'
canonical_url: 'https://larabench.com/laravel-tinker-workflows/inspect-laravel-config-and-services'
md_url: 'https://larabench.com/laravel-tinker-workflows/inspect-laravel-config-and-services.md'
last_updated: '2026-07-28'
---
# Inspect Laravel config and service container bindings

> Use Tinker to read config values, resolve services, and confirm runtime bindings without adding temporary routes or debug controllers.

## Direct Answer

Use Tinker to inspect the config and service container values that Laravel actually booted with. In LaraBench, save the snippet and review its structured output in History.

## When To Use This

Use this when an app behaves differently between environments, or when a binding changes after config cache, service provider changes, or package upgrades.

## Terminal Approach

```bash
php artisan about
php artisan tinker --execute="dump(config('queue.default'));"
```

## LaraBench Approach

Open Run Code, choose the target app, paste the inspection snippet, save it once useful, and use History to compare the same keys across environments.

## Snippet

```php
use Illuminate\Contracts\Cache\Repository as CacheRepository;
use Illuminate\Support\Facades\App;

return [
    'app_env' => config('app.env'),
    'queue_default' => config('queue.default'),
    'cache_store' => config('cache.default'),
    'cache_class' => get_class(App::make(CacheRepository::class)),
];
```

## Expected Result

The result should be a small array with the runtime environment, queue driver, cache store, and concrete cache repository class.

## Troubleshooting

- If config values differ from `.env`, check whether the app is using cached config.
- If a binding fails to resolve, confirm the package service provider is registered in this environment.
- If output is too large, return a named array of specific keys instead of dumping full services.

## Safety Notes

Do not print secrets, tokens, mail credentials, private URLs, or entire config arrays into shared screenshots or saved history.

## Related Sources

- [Laravel configuration documentation](https://laravel.com/docs/13.x/configuration)
- [Laravel service container documentation](https://laravel.com/docs/13.x/container)
- [LaraBench Saved snippets docs](https://larabench.com/docs/basic-usage/saved-snippets)

## Related Workflows

- [Check Laravel production with a read-only Tinker snippet](https://larabench.com/laravel-tinker-workflows/safe-laravel-production-check)
- [Inspect Laravel routes and middleware](https://larabench.com/laravel-tinker-workflows/inspect-laravel-routes-and-middleware)

## Canonical Page

- [HTML page](https://larabench.com/laravel-tinker-workflows/inspect-laravel-config-and-services)
- [Markdown mirror](https://larabench.com/laravel-tinker-workflows/inspect-laravel-config-and-services.md)

## Glossary

- [Laravel workflow glossary](https://larabench.com/docs/reference/glossary)

## Sitemap

See the full [sitemap](https://larabench.com/sitemap.md) for all public pages.