How are people storing tenant-specific settings?
Using the multi-tenancy pattern described in the Filament docs (using a single database with a single
Tenant model), how are people storing/configuring tenant-specific settings? Usually I'd reach for something like spatie/laravel-settings and the related Filament plugin, but it's not tenant-aware and so the settings end up being global settings (e.g. settings that I would set to control the entire site, rather than being configurable by each individual tenant).
How are people addressing this problem? I'd rather not have 100 different columns on each Tenant object if I don't have to, and I'd rather use a package than roll my own if possible. I can't imagine that I'm the first person to encounter an issue like this so I'm curious how others solved it.
ThanksSolution:Jump to solution
Went through this rabbit hole recently. Ended up rolling our own, as we required inheritance (platform > tenant > company). I came across https://randallwilk.dev/docs/laravel-settings/v3/basic-usage/teams during my search, which I hope does what you are looking for (you can replace team with tenant).
Teams - laravel-settings
laravel-settings
2 Replies
Solution
Went through this rabbit hole recently. Ended up rolling our own, as we required inheritance (platform > tenant > company). I came across https://randallwilk.dev/docs/laravel-settings/v3/basic-usage/teams during my search, which I hope does what you are looking for (you can replace team with tenant).
Teams - laravel-settings
laravel-settings
Oh man, this looks great. Thank you!