- What Laravel and PHP versions does this package support?
- The package requires **PHP 8.4+** and is designed for **Laravel 10+**. Ensure your project meets these minimum requirements to avoid compatibility issues. Check the [GitHub releases](https://github.com/baks-dev/users-profile-user/releases) for version-specific details.
- Does this package create a separate profiles table or extend the existing users table?
- The package creates a **separate profiles table** (likely named `profiles`) linked to the users table via a foreign key. This modular approach avoids cluttering the users table while maintaining clean relationships. You can inspect the Doctrine migrations for exact schema details.
- How do I install and configure the package in my Laravel project?
- Run `composer require baks-dev/users-profile-user`, then execute `php artisan baks:assets:install` to set up resources. For database changes, use `php artisan doctrine:migrations:diff` and `php artisan doctrine:migrations:migrate`. No additional config file is required unless customizing fields or storage.
- Can I customize profile fields (e.g., add a 'bio' or 'avatar') without forking?
- Yes, the package supports **customization via Doctrine migrations** and service provider extensions. Override existing migrations or create new ones to add fields. For UI changes, extend Blade templates or use Laravel’s view composers. Check the `config` directory for configurable options.
- How does this package handle profile images or media storage (e.g., S3, local filesystem)?
- The package defaults to **local filesystem storage** but can be extended to support S3 or other adapters via Laravel’s filesystem configuration. Modify the `filesystem_disks` setting in your `.env` or override the storage logic in the service provider. No built-in S3 support exists out of the box.
- Does the package integrate with Laravel’s authentication systems (e.g., Sanctum, Passport)?
- No, the package **does not natively integrate** with Sanctum, Passport, or Laravel Gates. You’ll need to manually implement middleware or policies (e.g., `updateOwnProfile`) to restrict profile access. Use Laravel’s built-in authorization features to bridge the gap.
- Are there REST/JSON:API endpoints for profiles, or do I need to build them?
- The package **does not include built-in API endpoints**. You’ll need to create custom routes, controllers, or API resources (e.g., using Laravel’s `Route::apiResource`) to expose profile data. The package provides the data model; endpoints are left to your discretion.
- How do I run the included PHPUnit tests for this package?
- Execute `php artisan test --group=users-profile-user` to run the package’s test suite. Tests are grouped under `users-profile-user`, so this ensures only relevant tests are executed. For custom test scenarios, extend the existing test classes or create new ones in your project’s `tests` directory.
- What are the risks of using Doctrine migrations in a Laravel project that already uses Eloquent?
- Doctrine migrations may **conflict with Eloquent’s schema expectations**, especially if your project uses raw queries or custom table structures. Audit your existing migrations and schema before integrating to avoid data loss. Consider using Eloquent migrations if your project relies heavily on Eloquent.
- Is this package actively maintained, and what’s the upgrade path if breaking changes occur?
- The package has **no visible community activity** (0 stars) and was last updated in 2026, raising concerns about long-term maintenance. No deprecation policy or breaking change guidelines are documented. Monitor the [GitHub repo](https://github.com/baks-dev/users-profile-user) for updates or consider forking if critical changes are needed.