Weave Code
Devdb Laravel Package
pinoox/devdb
Pinoox DevDB is a developer-focused database toolkit for Pinoox PHP applications. It offers schema helpers, query utilities, and debugging support to simplify data modeling, migrations, and seeding so you can build data-driven features faster with less boilerplate.
A zero-configuration development database for PHP
Frequently asked questions about Devdb
- What is pinoox/devdb used for?
- pinoox/devdb is a developer-focused database toolkit for Pinoox PHP applications. It bundles utilities for inspecting schema such as tables, columns and relationships, running and debugging queries, reviewing database structure, and producing repeatable seed data during development. The aim is to cut boilerplate so you can model and test data-driven features faster without leaving your Pinoox workflow.
- How do I install pinoox/devdb with Composer?
- Add it as a Composer dependency in your Pinoox project, ideally as a development-only requirement since it is a developer aid rather than runtime code: composer require --dev pinoox/devdb. After installation, follow the package README for any registration or configuration step, because setup conventions differ between Pinoox releases.
- Does pinoox/devdb work with Laravel applications?
- No. It targets Pinoox and does not ship Laravel service providers or Artisan commands, so dropping it into a Laravel app will not give you the expected workflow. Laravel teams should look at built-in tooling such as db:show, db:table, seeders and Telescope, or query-panel packages like laravel-debugbar. The ideas are similar, but the integration points here are Pinoox-specific.
- Which PHP and Pinoox versions are supported, and is the package maintained?
- Version support is defined by the require constraints in the package composer.json, so check that file and the release history before adding it to an existing project. Because it is a development tool, pinning a major version and reading the changelog on upgrade is the safest approach. If you run an older Pinoox release, confirm compatibility with the maintainer before depending on the toolkit.
- How do I inspect tables, columns and relationships with pinoox/devdb?
- The package provides inspection utilities that list tables, describe their columns and surface relationships, so you can review a schema without switching to a raw SQL client. This is most useful while designing migrations or onboarding to an unfamiliar database. Exact commands and output formats are documented in the README; treat them as development-only helpers.
- Can I use pinoox/devdb to debug slow or failing queries?
- It includes query utilities for running and debugging SQL during development, which helps you see what a statement does and why it fails before wiring it into application code. It is not a production monitoring or APM tool, so pair it with your normal logging and a profiler for performance work. Keep query dumping disabled outside local environments to avoid leaking data.
- How do the development seeding helpers work?
- Seeding helpers let you define repeatable test data so a fresh or reset database can be repopulated consistently. That keeps local fixtures and test runs predictable instead of hand-crafting rows each time. Keep seeds small and composable, and keep them out of production deployment paths.
- Is there anything to configure after installing pinoox/devdb?
- Configuration depends on your Pinoox version and how the package registers itself, so follow the README setup section rather than assuming Laravel-style config publishing. Typical adjustments are the database connection used and any environment guards that keep the tooling out of production. Commit shared settings and keep environment-specific values in your env file.
- Is pinoox/devdb safe to run in production?
- It is designed for development, so treat it as a require-dev dependency and make sure its inspection and query-execution utilities are disabled or unreachable in production. Exposing schema dumps or ad-hoc query running publicly would be a serious information-disclosure risk. If you must run it elsewhere, gate it behind an environment flag and authorization middleware.
- How does pinoox/devdb compare to alternatives?
- Alternatives include a dedicated database client such as TablePlus, DBeaver or phpMyAdmin, raw SQL through Pinoox's query builder, or a general PHP debugging tool; each covers inspection without touching application code. pinoox/devdb's value is staying inside the Pinoox workflow with seeding helpers and query utilities in one place. If you need broad ecosystem support or Laravel-first tooling, those alternatives fit better.
Weaver
How can I help you explore Laravel packages today?