- How do I install arcanesoft/auth in a Laravel application?
- Install it with Composer using composer require arcanesoft/auth. Because this package is the authorization layer for ARCANESOFT/Foundation, you will usually need the foundation package installed and configured first. After that, publish any package configuration or migrations and follow the repository README for wiring up the service provider and routes.
- Which Laravel versions are supported by arcanesoft/auth?
- The package targets Laravel applications, but the exact Laravel and PHP constraints come from its composer.json and its dependency on ARCANESOFT/Foundation. Check those requirements before installing, especially if you are on an older or very new Laravel release. The repository tags and CI configuration are the best place to confirm tested versions.
- Does arcanesoft/auth provide roles and permissions out of the box?
- Yes. The package description lists roles and permissions as part of its authentication and authorization feature set. You will still need to assign roles and permissions to users and protect routes with the appropriate middleware or gates. Review the published configuration and models to see how role and permission checks are exposed.
- How do I set up email verification with arcanesoft/auth?
- Email verification is included in the package's authentication flow, so users can confirm their email address before accessing protected areas. You must configure Laravel's mail settings and make sure your user model and routes use the package's verification flow. Check the README for the exact middleware, route names, and notification classes to publish or configure.
- Can I customize authentication guards in arcanesoft/auth?
- Yes, customizable guards are one of the package's advertised features. Guard behavior is typically configured in Laravel's config/auth.php along with any package-specific configuration. Confirm the guard names the package expects before changing defaults, since routes and middleware may reference them.
- Is arcanesoft/auth a replacement for Laravel Breeze or Jetstream?
- Not exactly. Breeze and Jetstream are first-party Laravel starter kits, while arcanesoft/auth is a Foundation-oriented package that bundles authentication with roles and permissions. It is a natural fit if you already use ARCANESOFT/Foundation, but for a standard Laravel app you may prefer Breeze, Jetstream, or spatie/laravel-permission.
- How do I run the tests for arcanesoft/auth?
- As a Composer package, it should expose its test setup through composer.json scripts, commonly composer test or vendor/bin/phpunit. Check the repository's CI workflow for the exact commands and any required database or mail services. When integrating into an app, add feature tests covering login, registration, password reset, and authorization checks.
- Is arcanesoft/auth safe and maintained for production use?
- It is a small, Foundation-specific package, so review its release history, open issues, and compatibility with your Laravel version before using it in production. Pin a tagged release and audit the authentication and authorization code paths that matter to your app. If long-term maintenance is critical, plan for the option of forking it or choosing a more actively maintained alternative.
- How do I configure password reset with arcanesoft/auth?
- Password reset is part of the package's built-in authentication system, but it still relies on Laravel's password broker and mail configuration. Configure your mail driver, users table, and password reset tokens as you would for any Laravel app, then check the package routes and notifications. Test the complete reset flow in a staging environment before enabling it for users.
- Why does arcanesoft/auth require arcanesoft/foundation?
- The package is described as the authorization package for ARCANESOFT/Foundation, which means it builds on that foundation's service providers, configuration, and conventions. Installing it without the foundation can lead to missing classes, unpublished config, or unresolved route middleware. If you want a standalone auth solution, a first-party Laravel starter kit or a package like spatie/laravel-permission may be a better fit.