- How do I install Laravel Truss in a Laravel application?
- Install it as a dev dependency with composer require --dev albertoarena/laravel-truss, then visit the /truss route in your app. Nothing needs to be published to get started. The package is auto-discovered, and its config is publishable when you need to customize it.
- Does Laravel Truss support Laravel 10 or Laravel 11?
- No. Laravel Truss has a hard version floor of PHP 8.2+ and Laravel 12+. Applications still on Laravel 10 or 11 are excluded outright, so check your framework and PHP versions before adopting it.
- Does Laravel Truss expose or query my row data?
- No. Laravel Truss reads structure only, including tables, columns, keys, and indexes, and never queries or exposes row data. The structure-only guarantee is stated consistently across the CLI, facade, and export pipeline.
- How do I secure the Laravel Truss route in production?
- The /truss route is gated, and the package exposes a viewTruss gate for authorization. If you use Truss outside local development, you need an explicit gate policy such as role-based access, SSO-backed checks, or a config allowlist. Even gated, the route reveals table names, columns, indexes, and foreign keys, so treat it as a sensitive surface and assign an owner.
- Can Laravel Truss handle multiple database connections?
- Yes. Laravel Truss supports multiple connections through a connection picker, per-connection excluded_tables settings, and URL-persisted selection. This makes modular monoliths and main-plus-module database topologies first-class rather than an afterthought.
- Does Laravel Truss require Node.js or a frontend build step?
- No. Laravel Truss vendors Mermaid and its fonts, so there is no CDN dependency and no Node build step. That keeps it CSP-safe and easy to run in Composer, Artisan, and CI-based Laravel environments.
- How does the Laravel Truss schema snapshot stay up to date?
- Laravel Truss uses a cached schema snapshot that is rebuilt after migrations. Out-of-band DDL such as manual hotfixes, DBA changes, or restored dumps may not invalidate it, so the diagram and related diff or doctor outputs can appear stale. That is a correctness edge rather than a crash risk, but it matters if you rely on the snapshot for accurate schema review.
- Is Laravel Truss actively maintained and safe to depend on?
- Laravel Truss is well-built, with tests, a changelog, releases, documentation, accessibility checks, a live demo, and video coverage. The main risk is lifecycle and supply chain: it has a single maintainer, around 288 stars, and zero Packagist dependents. Treat it as a tool you could fork rather than critical production infrastructure.
- Which database drivers does Laravel Truss support?
- Laravel Truss reads schema through Laravel's connection layer and does not introduce migrations or schema changes. The README does not enumerate supported database engines, and introspection is exactly where driver-specific gaps can appear. Verify behavior on your target driver, especially Postgres schemas, SQL Server, and SQLite quirks.
- Can I use Laravel Truss in staging or production?
- You can, but it is a deliberate decision. A --dev install is stripped by composer install --no-dev, so staging or production use requires promoting Truss to a regular dependency, which ships the package, route, views, and assets in the production artifact. If you do that, secure the viewTruss gate and assign ownership, or restrict Truss to local-only use.