Weave Code
Multitenancy Nova Tool Laravel Package
romegadigital/multitenancy-nova-tool
A Laravel Nova tool for multitenancy that helps you manage tenants and switch tenant context from within Nova, simplifying multi-tenant administration.
romegadigital/multitenancy-nova-tool adds a Laravel Nova interface for managing tenants in applications built with RomEga Digital’s multitenancy stack. It gives admins a central place to view and maintain tenant data without leaving the Nova dashboard.
- Tenant CRUD from a dedicated Nova tool
- Domain/hostname management per tenant
- Fast tenant switching and context awareness
- Integrates with romegadigital/multitenancy
- Configurable setup for existing Nova apps
Frequently asked questions about Multitenancy Nova Tool
- What is romegadigital/multitenancy-nova-tool?
- It is a Laravel Nova tool that adds an admin interface for viewing, creating, and switching tenants in a multi-tenant application. It integrates with Romega Digital's multitenancy package rather than providing tenancy itself. The repository is archived, so treat it as a UI reference or fork candidate, not an actively maintained dependency.
- Is this package maintained or archived?
- The repository is archived, meaning no upstream fixes, security patches, or Nova and Laravel compatibility updates. You will own maintenance if you adopt it. Evaluate a fork with pinned dependencies and automated tests before production use.
- Which Laravel and Nova versions does it support?
- The provided context does not list exact Composer constraints; the package is a Nova tool and expects a Laravel app with Laravel Nova installed. Because it is archived, constraints are likely stale for Laravel 10+ and Nova 4+ environments. Verify composer.json against your PHP, Laravel, Nova, and tenancy package versions before installation.
- Which multitenancy package does it integrate with?
- It is described as integrating with Romega Digital's multitenancy package, not stancl/tenancy or spatie/laravel-multitenancy by default. Confirm the exact package name and version targeted by the last release. If your tenancy implementation differs, use the UI as a pattern rather than installing it as-is.
- How do I install it with Composer?
- Installation would typically be a Composer require plus Nova tool registration in your Nova service provider, but the archived status and stale constraints make a direct install risky. Fork the repository, pin dependencies, and test in a non-production branch first. Follow Nova's tool registration documentation for your Nova version.
- Can I use this for database-per-tenant provisioning?
- The tool is an admin UI layer, not a provisioning engine. It may encode assumptions about tenant models, domains, database connections, caches, queues, and rollback behavior, but those must be verified against your tenancy package. Do not assume it safely provisions or tears down tenant databases without isolation tests.
- Does it enforce tenant isolation and authorization?
- Tenant isolation must be enforced server-side by your tenancy package and application code; a Nova UI alone is only an admin convenience layer. The context warns that incomplete provisioning or connection switching could cause cross-tenant data leakage. Add RBAC, audit logging, and approval gates before exposing destructive tenant actions.
- Is it safe for production?
- High risk for production as-is because it is archived and has zero dependents and low ecosystem validation. Use it only on a frozen Laravel and Nova stack that matches its assumptions, after a fork, dependency audit, and isolation tests. Do not expose it to production admins until provisioning, rollback, domain conflicts, and cross-tenant access are covered by automated tests.
- What are alternatives to this Nova tool?
- Build an internal Nova tool against your current tenancy package's API, or use the maintained admin features of stancl/tenancy or spatie/laravel-multitenancy if those match your architecture. You can also extract CRUD and workflow patterns from this repository and reimplement them for Laravel 10+ and Nova 4+. The right choice depends on your tenancy model and whether you need Nova specifically.
- How should I fork and maintain it?
- Fork into your organization, tag an internal version, pin all Composer dependencies, and add a compatibility matrix for PHP, Laravel, Nova, and the tenancy package. Check the repository license before internal redistribution and add CI tests for tenant creation, domain binding, database provisioning, cache and queue isolation, deletion, and rollback. Assign a maintainer and budget quarterly dependency reviews because upstream support is gone.
Weaver
How can I help you explore Laravel packages today?