- What is schmeits/pulse-panphp used for?
- It is a Laravel Pulse card that displays PanPHP analytics inside your Pulse dashboard. It lets you monitor page views, visitors, and traffic trends alongside application health metrics. It is a dashboard integration for PanPHP data, not a standalone analytics platform.
- How do I install schmeits/pulse-panphp?
- Install it with Composer using composer require schmeits/pulse-panphp, then follow the package README for any provider registration or config publishing. Laravel package auto-discovery may register the service provider automatically, but verify this in the package composer.json. After installation, clear your config and view caches and load your Pulse dashboard.
- Does schmeits/pulse-panphp require Laravel Pulse and PanPHP?
- Yes. By description, it is a Pulse card for PanPHP analytics, so you need Laravel Pulse installed and PanPHP collecting analytics data. Without PanPHP data, the card has nothing meaningful to display. Confirm the exact dependency constraints in the package composer.json before installing.
- Which Laravel and PHP versions does schmeits/pulse-panphp support?
- The provided release metadata does not list a PHP or Laravel constraint range, and version 0.0.1 is the first release. Check composer.json for require.php and illuminate/support or laravel/framework constraints before installing. Validate those constraints against your pinned PHP runtime and Laravel major version.
- How do I configure the PanPHP analytics card in Pulse?
- Configuration is package-specific, so look for a publishable config file or setup instructions in the README after installation. Typical steps include publishing config, supplying any PanPHP connection or API details, and registering the card where Pulse cards are configured. Clear the config cache after making changes.
- Is schmeits/pulse-panphp stable enough for production?
- Version 0.0.1 is pre-alpha by convention and carries no API stability guarantee. Before production use, review the package source, test coverage, CI status, license, and maintainer activity. For critical dashboards, pin the exact version and review changes before upgrading.
- Is schmeits/pulse-panphp privacy-friendly?
- PanPHP is described as privacy-friendly analytics, and this package only displays that data in Laravel Pulse. The card itself is not a full tracking system. Review PanPHP's data collection, storage, and retention settings to confirm they meet your compliance requirements.
- Does schmeits/pulse-panphp store analytics data or add database tables?
- The package is described as a Pulse card, so its role is displaying PanPHP analytics rather than owning the analytics data store. Any migrations or tables would more likely come from PanPHP or Pulse, but package details are limited at version 0.0.1. Verify the source and composer.json before assuming there are no schema changes.
- How does schmeits/pulse-panphp compare to using PanPHP directly?
- Using PanPHP directly gives you its APIs and reporting, while this package adds a Laravel Pulse card for dashboard-level visibility. The card is useful if your team already monitors Pulse and wants analytics next to health metrics. It adds one dependency link, so weigh that convenience against the extra package in your supply chain.
- What are the risks or alternatives to schmeits/pulse-panphp?
- The main risks are early maturity at version 0.0.1, unclear Laravel version tracking, and single-maintainer or bus-factor uncertainty. Alternatives include PanPHP's own reporting, a custom Pulse card, or a more mature analytics tool. Before adopting, audit the dependency tree, license, security disclosure process, and release cadence.