Weave Code
Db Console Laravel Package
laranail/db-console
A database console for Laravel: browse tables, run ad-hoc SQL, and inspect results in a lightweight Artisan-served UI. Configurable connection allowlists, read-only mode, and query guards keep production data safe, while Composer install and a published config get you running in minutes.
Self-hosted, multi-server database, user, and privilege management for Laravel — headless core with CLI and REST API.
Frequently asked questions about Db Console
- What is Laranail DB Console used for in a Laravel app?
- It adds a lightweight in-app database console so developers can browse tables, columns, and indexes, inspect schemas, and run ad-hoc SQL without leaving the browser. It reuses your existing Laravel database connections, so there is no extra service to configure. Access can be restricted with Laravel authorization and environment settings.
- How do I install laranail/db-console?
- Install it with Composer as a Laravel package, then publish its configuration file. The UI is served through Artisan, so you can start it from the command line after configuring connections and access. Use the exact install and publish commands from the package README for your Laravel version.
- Does it support multiple database connections?
- Yes, it can browse tables, columns, and indexes across configured connections. The package supports configurable connection allowlists, so you can limit which connections are exposed in the console. It reuses your existing Laravel database connections rather than requiring new credentials or a separate service.
- Can I run custom SQL queries with Laranail DB Console?
- Yes, it supports ad-hoc SQL queries with instant, paginated results. Query guards and read-only mode are available to help keep production data safe, according to the package blurb. Test queries in a staging environment and review the guard configuration before enabling it in production.
- Is Laranail DB Console safe for production use?
- The package is designed with production safety in mind: it offers read-only mode, query guards, connection allowlists, and Laravel authorization restrictions. However, any in-app database console increases risk if misconfigured, so restrict access via environment settings and policies. Start in a controlled staging environment and enable only the connections and operations you need.
- Which Laravel versions are supported by laranail/db-console?
- The provided context does not specify a Laravel version range, so check the package's composer.json requirements before installing. It is described as a Laravel package that uses Laravel's database connections and authorization features. Test compatibility with your application's Laravel version in a non-production environment first.
- How does Laranail DB Console restrict who can access it?
- Access can be restricted through Laravel authorization and environment settings. The package also supports configurable connection allowlists, read-only mode, and query guards as additional layers. Define Gates or Policies and keep the console disabled in environments where it is not needed.
- Can I search, sort, and filter table data in the interface?
- Yes, the package includes a clean interface for searching, sorting, and filtering table data. It also lets you browse tables, columns, and indexes and inspect schemas across configured connections. Results for ad-hoc SQL queries are paginated for easier inspection.
- How is it different from phpMyAdmin or a separate database admin tool?
- Laranail DB Console runs inside your Laravel app and reuses existing Laravel database connections, so you do not need a separate service or standalone admin tool. Unlike external tools, it can apply Laravel authorization and environment settings to restrict access. It is focused on browsing tables, inspecting schemas, and running guarded SQL rather than being a full standalone database administration suite.
- How should I test or evaluate laranail/db-console before production?
- Install it in a staging or local environment first, publish the config, and enable only a non-critical database connection. Use the connection allowlist, read-only mode, and authorization gates to simulate production restrictions. Review query guard behavior and confirm that pagination, sorting, and filtering work with your schema before rolling it out.
Weaver
How can I help you explore Laravel packages today?