Weave Code
Admin Laravel Package
larasell-dev/admin
A Laravel admin panel package that gives you a ready-made dashboard, resource CRUD screens, authentication and access control so you can ship back-office tooling fast without building the UI from scratch.
Larasell Admin is a Laravel package that provides a ready-to-use admin panel for managing application data. It offers a clean, customizable interface for building CRUD screens and handling common back-office tasks without leaving your Laravel stack.
- Resource-based CRUD for Eloquent models
- Authentication-ready admin access and authorization hooks
- Customizable UI with configurable navigation and layouts
- Laravel-native integration via service provider and config
- Extensible actions, fields, and filters
Frequently asked questions about Admin
- What are the requirements for installing larasell-dev/admin?
- Larasell Admin is a Laravel package built around Inertia.js pages and the @larasell-dev/ui component library, so you need a Laravel application with an Inertia frontend and a working Node/Vite build pipeline. Version 0.1.0 also depends on an early @larasell-dev/ui release (around 0.1.5), so your frontend dependencies must be compatible with it. Exact Laravel, PHP, Inertia, and Node constraints are not documented in the overview, so check the package's composer.json and package.json before installing. Verify package discovery, route registration, and asset publishing in a sandbox app first.
- Which Laravel and PHP versions does Larasell Admin support?
- The 0.1.0 release does not publish an explicit Laravel or PHP version matrix, so treat the constraints in composer.json as the source of truth. Because it is an early 0.x package, the supported range may be narrow or change between minor versions. Run a sandbox spike against your target Laravel version before committing to adoption. Pin the package and lock your Composer and npm dependencies to avoid unexpected drift.
- Do I need Inertia.js and @larasell-dev/ui to use Larasell Admin?
- Yes. Larasell Admin is built around Inertia pages and the @larasell-dev/ui package, so it is not a drop-in fit for Blade, Livewire, or other admin stacks. If your application already standardizes on Laravel with Inertia and Larasell UI, the panel should integrate naturally. Teams using a different frontend stack would need significant adaptation or should evaluate a different admin package.
- How do I install and configure larasell-dev/admin in a Laravel application?
- Install the package with Composer, then confirm that Laravel package discovery registers the service provider and routes. You will typically need to publish any config and assets, run the frontend build, and check whether migrations or storage links are required for features such as avatar uploads. Because the package is pre-1.0, follow the repository README for the exact publish tags and commands rather than assuming conventions. Validate the install in an isolated admin area before wiring it into an existing panel.
- Does Larasell Admin include login, authentication, and role-based access control?
- Version 0.1.0 includes login styling, profile management, avatar upload, a sidebar layout, mobile navigation, and a user menu, which points to an opinionated admin scaffold. The overview does not describe an authorization model beyond the concept of an admin user, and there is no evidence yet of RBAC, roles, or audit logging. You should review the login and profile flows for validation, guard compatibility, and authorization gaps. Many teams will need to add their own policies or role layer on top.
- How are routes, configuration, and assets published in Larasell Admin?
- The package ships Inertia pages and depends on @larasell-dev/ui, so it almost certainly requires publishing assets and running a Vite build, but the exact publish tags are not documented in the overview. Inspect the service provider for config, route, and asset publishing calls, and watch for route or middleware collisions with existing admin routes. Verify how the Inertia page resolver is configured so Larasell pages resolve correctly. Pin versions and document the publish and build steps for your team.
- How does avatar upload work and where are uploaded files stored?
- Profile management with avatar upload is listed as a feature, but the overview does not specify the storage disk, validation rules, or retention behavior. Review the upload request and controller code for file size, MIME type, and image validation, and confirm storage disk permissions and symlink setup. Plan a storage and CDN strategy, including cleanup of orphaned files. In production, treat uploads as a security-sensitive surface and test permissions explicitly.
- Can Larasell Admin coexist with my existing admin routes and middleware?
- It can, but coexistence needs testing. The panel registers its own routes and middleware assumptions, so check for route name collisions, prefix conflicts, and guard mismatches with your existing admin area. The safest approach is to mount it under a separate path or guard, or behind a feature flag in an internal-only admin. Validate navigation, redirects, and validation-error sharing after integration.
- Is larasell-dev/admin production-ready at version 0.1.0?
- Treat it as a pilot. Version 0.1.0 is the first release, has limited visible test coverage, and depends on an early @larasell-dev/ui version, so pre-1.0 risk is high. Security-sensitive flows such as login, profile updates, and avatar uploads need your own review for validation, authorization, and storage permissions. Adopt it in a new or isolated internal admin first and defer production-critical rollout until 1.0 or a documented stability commitment.
- What is the upgrade and maintenance policy before version 1.0?
- There is no published backward-compatibility policy yet, and breaking changes are likely across 0.x releases, potentially requiring coordinated changes to Inertia pages and the @larasell-dev/ui dependency. Pin exact versions, commit lockfiles, and monitor release notes before upgrading. Expect to own troubleshooting, security review, and upgrade testing internally. Ask the maintainers about support channels and the roadmap to 1.0 as part of due diligence.
Weaver
How can I help you explore Laravel packages today?