- Is webman/admin a Laravel package?
- No. webman/admin is a plugin for webman, the Workerman-based resident-process PHP framework, and it only boots inside a webman application. There is no Laravel service provider, no Artisan command surface, and no Laravel HTTP kernel binding, so it cannot be required into a Laravel app and expected to work. Treat it as the webman analogue of Filament or Nova rather than a Laravel package.
- Can I install webman/admin inside an existing Laravel application?
- Not in-process. In-process integration would require rewriting the plugin's bootstrap assumptions, which is not realistic for an evaluation. Only two shapes are viable: a sidecar admin service running webman/admin against the same database and schema as your Laravel app, or a standalone back-office app that fronts Laravel over HTTP APIs. Both mean two apps, two deploy pipelines, and duplicated auth and observability.
- How do I install webman/admin?
- It is installed with Composer and registered through webman's plugin mechanism, not through Laravel's package discovery. After installing you import the plugin's own database tables and configure its database connection and plugin config in the webman project. Because it is a full admin application, plan for its own runtime entry point, config directory, and deployment process rather than a drop-in dependency.
- What features does webman/admin include out of the box?
- It ships a complete backend UI with admin user management, RBAC roles and permissions, menu configuration, operation logs, attachments, and system settings. A one-click CRUD generator turns database tables into working controllers, models, routes, and Vue pages. The frontend is Vue-based and designed to be extended, and the whole panel installs as a modular webman plugin.
- Which ORM does the webman/admin CRUD generator assume?
- This is unverified and is one of the first things to check before committing. webman commonly pairs with think-orm, and although webman/database wraps illuminate/database so Eloquent models may be reusable, it is not documented whether the generated CRUD assumes think-orm conventions. Test the generator against your existing schema and models in a spike before relying on it.
- Can webman/admin authenticate against existing Laravel users, JWT, or SSO?
- By default it expects its own admin user table, and there is no documented bridge to Laravel-issued sessions or tokens. The practical options are a shared identity store, an upstream SSO proxy, or reverse-proxy authentication in front of the panel. Proving this auth bridge is the make-or-break step of any evaluation; if identity cannot be unified, stop there rather than expanding the scope.
- Which PHP and webman versions does webman/admin support?
- The plugin is pinned to specific webman core and PHP versions, so check its composer.json constraints against your environment before planning anything. If you run it as a sidecar next to a Laravel app, your PHP version must satisfy both runtimes simultaneously. Upgrades to webman core can affect the plugin, so pin versions and test upgrades rather than tracking latest.
- Is webman/admin production-ready, and what are the main risks?
- It is MIT licensed and functional, but the ecosystem signals are thin: roughly 377 stars, zero dependents, single-organization ownership, and documentation weighted toward Chinese-language sources. The bigger operational risks are runtime divergence from your Laravel stack, a second credential store widening the authenticated attack surface, and unclear security disclosure and release cadence. Pin versions, isolate the panel, and confirm named maintainers before production use.
- What are the alternatives to webman/admin for a Laravel admin panel?
- For a Laravel-first team the default recommendation is Filament or Nova, which are in-framework, in-ecosystem, and carry a fraction of the operational overhead. webman/admin only becomes a good fit if your organization already runs webman for high-throughput endpoints and has the operational muscle memory for it. If you need the generator and permission model specifically, budget a parallel evaluation rather than blocking your existing admin roadmap.
- Does webman/admin support multi-tenancy or custom domain logic beyond generic CRUD?
- Multi-tenancy is not documented, and the extension and hook points for custom domain logic beyond generic CRUD are unclear. The reusable value in the plugin is the generator and the RBAC permission model, but neither is exposed as a Laravel-compatible API. If your product needs tenant isolation or non-trivial business rules, verify these gaps during a short spike in a container against a cloned schema before committing.