- How do I install miracuthbert/laravel-royalty in a Laravel application?
- Install it with Composer using a caret constraint such as composer require miracuthbert/laravel-royalty:^1.4 in a non-production branch. After installation, publish the package configuration and migrations, review them against your existing schema, clear the config cache, and run your test suite. Check the installed package composer.json to confirm the actual Laravel and PHP constraints before promoting the lockfile.
- Which Laravel and PHP versions does laravel-royalty support?
- The 1.4.0 release notes say support was expanded from Laravel 7 to Laravel 10, but the exact supported range is ambiguous and should be confirmed in the installed composer.json. Laravel 10 requires PHP 8.1 or newer, while Laravel 7 and 8 can support older PHP lines, so align your PHP runtime before adopting the package. Review the package CI matrix for tested Laravel and PHP combinations.
- Can I use my own custom Point model with laravel-royalty?
- Version 1.4.0 makes the Point model configurable, so you can likely subclass the package model and register your override through the documented configuration or container mechanism. Before relying on this, verify whether the package requires an interface, a fixed table name, migrations, or relationship assumptions. Test model resolution and persistence after the override because internal concrete-class resolution can make customization breaking.
- Does laravel-royalty support real-time rewards or point updates?
- The package description mentions real-time support for rewards, loyalty, or experience points, but the release notes do not detail how that is implemented. Treat real-time behavior as something to validate against the package documentation and source, especially whether it uses Laravel events, broadcasting, or queued listeners. Do not assume WebSocket support without confirming the integration requirements.
- How do I award loyalty or experience points to users with laravel-royalty?
- The package provides an Eloquent-style Point domain model and model traits intended for tracking points, rewards, or loyalty balances. A typical flow is to create or update Point records associated with users through the package API, using configuration to resolve the model. Confirm the exact method names, relationships, and transaction behavior in the package documentation before building production logic.
- Is laravel-royalty for royalties and payouts or for loyalty and experience points?
- The context is inconsistent: the overview calls it a user points package for rewards, loyalty, or experience points, while the blurb describes royalties, earnings, and payouts. The technical assessment also asks whether Point is a geospatial entity or a loyalty and accounting entity. Validate the actual domain model and migrations before choosing it for either use case.
- How do I upgrade laravel-royalty to version 1.4.0 safely?
- Create a branch and update within the caret constraint, then inspect the installed composer.json to see the exact Laravel and PHP ranges. Publish and diff any configuration and migration changes, clear caches, and run both your application tests and package-specific integration tests. A minor release implies backward compatibility, but widening the framework matrix can expose deprecations and transitive dependency conflicts, so promote through staging with a committed lockfile.
- What are the risks of customizing the Point model in laravel-royalty?
- Custom model support is usually additive, but it can break if the package previously resolved a concrete class internally or if migrations and relationships reference a fixed table name. Check whether there is a documented contract or interface to implement and whether table names and domain assumptions are configurable alongside the model. Run integration tests for model resolution, table mapping, and persistence before upgrading.
- How should I test laravel-royalty before using it in production?
- Install it in a non-production environment with a pinned caret constraint, publish configuration and migrations, and diff the schema against your existing database. Clear the config cache and run your application test suite plus focused tests for model resolution, table mapping, persistence, and any real-time behavior. Promote to staging with a committed lockfile and avoid floating versions in production.
- What should I check about laravel-royalty maintenance and alternatives?
- Review the maintainer's release cadence, support policy, upgrade guide, and CI matrix because the supplied assessment notes limited release detail. Compare it with a custom point ledger or other Laravel loyalty packages if you need guaranteed long-term support or clearer contracts. Pin versions and verify compatibility with your Laravel and PHP lines before committing.