- What does schmeits/pulse-database-table-sizes do?
- It is a Laravel Pulse card that displays database table information, including table sizes, on your Pulse dashboard. It helps developers spot large tables and monitor storage growth at a glance. The package is installed via Composer and added to a Laravel Pulse dashboard.
- How do I install schmeits/pulse-database-table-sizes in Laravel?
- Install the package with Composer using composer require schmeits/pulse-database-table-sizes. Then register or add the card to your Laravel Pulse dashboard configuration as described in the package README. After installation, verify the card appears and shows table size data for your application database.
- Does this package require Laravel Pulse?
- Yes, schmeits/pulse-database-table-sizes is a card for Laravel Pulse, so Pulse must be installed and configured in your Laravel application. The card relies on the Pulse dashboard to display database table information. Check the package README for any additional installation or registration steps.
- Which Laravel and PHP versions does schmeits/pulse-database-table-sizes support?
- The supplied release context does not list the exact Laravel and PHP versions supported by version 1.7.2. Check the package composer.json and README before upgrading or installing it in an older application. This is especially important if you are running a Laravel version near the package support boundary.
- How do I configure table size precision in version 1.7.2?
- Release 1.7.2 adds a configurable precision setting for table size, sourced from PR #14. The exact config key and default value are not included in the supplied context, so review the package config file or README after upgrading. Set the desired precision value and clear cached configuration so the change takes effect.
- Does the precision setting affect stored data or only dashboard display?
- The supplied assessment does not confirm whether precision affects display formatting only or stored, compared, or exported values. In many Laravel packages, a precision setting is presentation-focused, but you should verify this in the package source or documentation. Check downstream dashboards, exports, alerts, or API responses if table size is surfaced outside Pulse.
- Why is my table size precision setting not taking effect after deployment?
- Laravel caches configuration, so a changed precision value may not apply until the config cache is rebuilt. Run php artisan config:clear during non-production validation and rebuild the config cache as part of deployment. Then verify representative table-size output on the Pulse dashboard.
- Can I use this package in production to monitor database growth?
- Yes, it is intended as a Laravel Pulse dashboard card for spotting large tables and monitoring storage growth. Treat the 1.7.2 precision update as a configuration change and validate it in staging first. Monitor the dashboard after deployment for formatting or reporting regressions.
- Is version 1.7.2 of schmeits/pulse-database-table-sizes safe to upgrade?
- Version 1.7.2 is a minor release adding configurable precision, so it should be backward-compatible. The supplied assessment still recommends confirming that the default precision preserves prior behavior. Review PR #14, the changelog, and package tests before upgrading production applications.
- What are alternatives to this package for monitoring Laravel database table sizes?
- Alternatives include querying database metadata directly, using relevant built-in Laravel Pulse cards, or other Pulse cards that report database or storage metrics. Choose based on whether you need table-level sizes, historical growth tracking, or simple dashboard visibility. This package is focused on showing table size information on a Pulse dashboard.