Download the PHP package mapo-89/core-panel-tenancy without Composer
On this page you can find all versions of the php package mapo-89/core-panel-tenancy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mapo-89/core-panel-tenancy
More information about mapo-89/core-panel-tenancy
Files in mapo-89/core-panel-tenancy
Package core-panel-tenancy
Short Description Optional stancl/tenancy bootstrap addon for Laravel CorePanel.
License MIT
Informations about the package core-panel-tenancy
Laravel CorePanel Tenancy
mapo-89/core-panel-tenancy is the optional stancl/tenancy addon for Laravel CorePanel.
Read-only split repository: this package repository is automatically synchronized from
mapo-89/core-panel-monorepo. Do not open pull requests or make direct changes here. All development happens in the monorepo.
The tenancy addon extends the core package with tenant-aware routes, settings, migrations, assets, and user workflows while keeping the core package tenancy-neutral.
Install
Existing Laravel app with CorePanel already installed:
If you install through the CorePanel installer, the addon can also be pulled in during php artisan core-panel:install.
Timestamp Conversion
When the tenancy addon is installed, the CorePanel timestamp conversion command also supports tenancy metadata tables and tenant databases:
Host applications can extend the conversion lists for addon-specific or project-specific tables in config/core-panel.php under:
core-panel.database.timestamp_tz_conversion.datasets.tenancycore-panel.database.timestamp_tz_conversion.datasets.tenant
The conversion uses the configured source timezone from core-panel.database.timestamp_tz_conversion.legacy_timezone and converts directly to timestamptz, so the stored instant does not depend on the PostgreSQL session timezone.
Update
Upgrading To 1.6.0 (Breaking)
CorePanel Tenancy 1.6.0 must be updated together with CorePanel 1.6.0 because central and tenant migration ownership, generated route handling, and package/host composition change.
Back up the central and tenant databases and commit or back up the host application before running:
The addon now owns its central migrations and tenant-specific package overrides. Existing migration ledger entries remain valid because migration basenames are preserved. Recognized unchanged host copies are backed up and removed; locally modified migrations remain in the host as conflicts and require manual review. A preserved migration under database/migrations/tenant overrides a package migration with the same basename, while unrelated custom tenant migration paths remain configured.
After updating, verify the central login, tenant provisioning, tenants:migrate, tenant authentication logs, generated central and tenant Wayfinder routes, and the frontend build. Use --breaking-changes only for this one-time 1.6.0 transition. Later 1.6.x updates use the normal commands below.
Update the addon inside an installed application:
If you usually update CorePanel and the addon together, prefer:
That path refreshes core and addon assets first and then runs the host application's outstanding migrations once.
Typical update runbook for an existing installation with the addon:
If generated assets such as resources/js/actions, resources/js/routes, resources/js/wayfinder, public/build, or public/hot were previously committed, remove them from the Git index once after adopting the new .gitignore:
Local Package Development
For local development from the monorepo:
License
CorePanel Tenancy is released under the MIT license.
