There are many different ways to handle data separation and isolation when it comes to multitenancy, each with their own trade-offs. There's also a very common misconception that to achieve multitenancy, each tenant must have its own database. Not only is that not true, it's also often not the best approach.
Recent Articles
You Probably Don't Need a Database Per Tenant
Explainer
29 Minutes Read
TheGamePanel: A Modern Alternative to Pterodactyl
Meta
10 Minutes Read
After years of working with existing game server panels, I'm building my own. The Game Panel is a modern alternative to Pterodactyl and Pelican, built from the ground up on a purpose-built PHP framework with a modular architecture designed for hosts and server owners alike.
Composer Run Dev and Laravel Sail
Tutorials
7 Minutes Read
If, like me, you're a user of Laravel Sail for some of your Laravel projects, you'll have probably noticed that the default 'composer run dev' command that ships with Laravel, just won't work for you. Well, I've got a solution for you!
Recent Projects
Cartograph
experimental
Cartograph is a Minecraft server directory that ranks listings by measured server quality rather than vote-buying or paid placement. Quality scores are derived from telemetry collected by an opt-in server-side plugin.
The Game Panel
active
In Development
A new open-source game server panel built from the ground up — modular by architecture, Wings-compatible out of the box, with granular RBAC and a first-class module system.
Composer Local Repositories
stable
1.0
A Composer plugin that adds support for local repository overrides via a repositories.local.json file, without modifying your project's core composer.json.
More on Laravel and multitenancy
Deep dives into how Laravel works, multitenancy, package releases, the occasional opinion piece. Roughly monthly.