Weave Code
Arkhe Main Laravel Package
adhocrat-io/arkhe-main
Bootstrap a Laravel admin backend with Livewire 4 + Flux UI: users, roles & permissions (Spatie), user profiles, SEO + sitemap, and cookie-consent. Interactive installer publishes config/migrations, seeds default roles, and patches sidebar/Tailwind scanning.
At a glance
Frequently asked questions about Arkhe Main
- Can I use this package with Laravel 11 or older versions?
- No, Arkhe-main requires Laravel 12 or 13 and PHP 8.3. If you're on an older version, you’ll need to upgrade first, which may involve significant refactoring, especially if using Livewire 3 or other legacy dependencies.
- What happens if I don’t need role-based access control (RBAC)?
- The package includes Spatie’s Laravel-Permission by default, which adds complexity even if unused. If RBAC isn’t critical, consider alternatives like Laravel Breeze or Jetstream, which offer simpler auth without permission layers.
- How do I customize the Flux UI admin dashboard without breaking updates?
- Arkhe-main publishes views, so you can override them in your project’s `resources/views/vendor/arkhe` directory. However, deep customizations may require patching core templates, increasing maintenance overhead during package updates.
- Does this package work with non-Flux UI frameworks like Inertia.js or Alpine.js?
- No, Arkhe-main is tightly coupled with Flux UI Free. While you can extract the permission logic (Spatie Laravel-Permission), the UI components and Livewire 4 integration are Flux-specific. For other frontends, consider standalone RBAC packages.
- Will this package slow down my Laravel application in production?
- The package adds SEO, sitemap, and cookie-consent features, which introduce HTTP overhead. For high-traffic apps, optimize by caching sitemaps (via `spatie/laravel-sitemap`) and disabling unused features in `config/arkhe.php`.
- Can I integrate Arkhe-main with existing auth systems like Sanctum or Passport?
- Potential conflicts may arise since Arkhe-main extends the `users` table and seeds default roles. Test thoroughly, and back up your database before running migrations. If using Sanctum or Passport, ensure their middleware aligns with Arkhe’s permission logic.
- What if I need advanced Flux UI features like dark mode or premium components?
- The free edition of Flux UI lacks these features, and Arkhe-main doesn’t include them. You’d need to upgrade to Flux Pro or build custom components, which may require overriding Arkhe’s views or extending its layout system.
- How do I handle migrations if I already have a custom `users` table?
- The installer adds profile columns (`first_name`, `last_name`, etc.) to the `users` table. If your table is customized, manually merge the migration or use a database diff tool. Always back up before running `php artisan migrate`.
- Is there a way to use Arkhe’s permission system without the Flux UI?
- Yes, you can install `spatie/laravel-permission` separately and reuse Arkhe’s config/migrations by publishing them manually. However, the Livewire 4 and Flux UI integrations won’t work, so you’d need to rebuild those parts.
- What’s the long-term support plan for this package? Should I rely on it for production?
- Arkhe-main is part of a new `adhocrat-io/arkhe-*` namespace with no active stars or dependents, indicating unproven maturity. For production, consider it a starting point but plan for potential maintenance gaps. Document customizations thoroughly in case the package evolves or is deprecated.
Weaver
How can I help you explore Laravel packages today?