Weave Code
Site Stats Laravel Package
capell-app/site-stats
Site Stats is a Laravel package for the Capell app ecosystem that provides site statistics and analytics, giving developers a simple way to collect and display visitor and usage data within their applications.
Simple content totals and metric trends for Capell sites.
Frequently asked questions about Site Stats
- What is capell-app/site-stats used for?
- capell-app/site-stats is a Laravel package from the Capell application ecosystem that provides privacy-safe aggregate site statistics and analytics. It is intended to help developers collect and display visitor and usage data inside Capell-based applications. The package follows Laravel package conventions and is distributed via Composer. It is currently published as a beta release, so confirm its feature set before relying on it as a system of record.
- How do I install capell-app/site-stats in a Laravel app?
- Install it with Composer using composer require capell-app/site-stats, then publish any provided configuration and migrations if the package supports them. Because it is a Laravel package, verify auto-discovery or register the service provider manually if needed. Run the migrations against a staging database first and inspect the generated schema. Pin the beta version rather than using a floating constraint.
- Is capell-app/site-stats compatible with my Laravel and PHP version?
- The overview does not publish explicit Laravel and PHP version constraints, so inspect the package composer.json before installing. Check the laravel/framework and php requirements against your application stack. Also verify database driver support, such as MySQL, PostgreSQL, or SQLite. If constraints do not match, test in a disposable branch before committing.
- Does capell-app/site-stats work outside the Capell CMS ecosystem?
- The package is described as part of the Capell CMS ecosystem, so standalone Laravel applications should validate assumptions around routing, middleware, authentication, and storage. It may depend on Capell-specific models, service bindings, or conventions that require adaptation. Review the source and configuration after installation to confirm whether Capell is a hard dependency. For non-Capell apps, treat integration as a spike rather than a drop-in install.
- What visitor data does capell-app/site-stats collect, and is it GDPR-friendly?
- The package is described as privacy-safe and aggregate, but the overview does not enumerate exactly what is captured. Before rollout, inspect the source, config, and migrations for fields such as IP addresses, user agents, URLs, or user IDs. Confirm whether data is aggregated or stored per request, and document retention and consent requirements. Validate the behavior against your GDPR or privacy policy rather than relying on the marketing description.
- Is capell-app/site-stats production-ready at v1.0.0-beta.41?
- Treat v1.0.0-beta.41 as beta software rather than a stable production dependency. Beta versioning means no semver stability guarantee, and beta-to-beta upgrades can include schema, config, or behavioral changes. The available release note is only a changelog comparison link, so upgrade risk is elevated. Use it in production only after testing migrations, rollback, and data privacy in staging.
- How do I upgrade capell-app/site-stats between beta releases?
- Read the full GitHub compare diff and migration files between your current beta and the target beta before upgrading. Back up analytics tables, run migrations against a staging copy, and verify rollback. Do not assume beta-to-beta upgrades are non-destructive or that config keys remain unchanged. Pin the exact beta version in composer.json and upgrade deliberately.
- Does capell-app/site-stats track requests synchronously or use queues?
- The overview does not state whether tracking runs synchronously in the request lifecycle or through queued jobs. Inspect the package middleware, event hooks, and service provider to determine how writes are performed. If tracking is synchronous, assess the write amplification and latency impact on high-traffic routes. If queues are involved, confirm your queue configuration and worker reliability.
- How can I test capell-app/site-stats before enabling it in production?
- Install the package in a spike branch or local environment, publish its config and migrations, and run migrations against a staging database copy. Enable tracking behind a feature flag or a limited route set, then compare captured data against expected traffic. Check whether admin, API, or health-check routes are tracked by default. Roll out to staging and then canary before enabling globally.
- What are alternatives to capell-app/site-stats for Laravel analytics?
- Alternatives depend on whether you need aggregate, privacy-safe metrics or full product analytics. Laravel teams often compare lightweight first-party tracking packages with services such as Plausible, Fathom, or Matomo, and with custom event logging. Evaluate capell-app/site-stats specifically if you are already in the Capell ecosystem and want Composer-based integration. Otherwise, confirm maintenance activity, release notes, and Laravel version support before choosing it.
Weaver
How can I help you explore Laravel packages today?