Filament•13mo ago

Multi tenancy with multiple database support

When reading the documentation, it appears that Filament only supports multi-tenancy with a single database by using team_id. Is implementing multiple databases in the plan, or is it easily achievable with a workaround, or do I need to use a third-party package like stancl/tenancy or spatie/laravel-multitenancy?

54 Replies

Dennis Koch•13mo ago

It’s not planned. Best to use a 3rd party plugin.

EleventhTower•13mo ago

Hmm. I need this functionality as well. I do not see any plugins that support multi-database tenancy. From searching the Discord chats here for Spatie Laravel-multitenancy, I see many problems, but none have a clear resolution. I read an old (2022) GitHub post, but the methods they listed to get it to work don't seem to map to V3 since the configuration file structure is different. There may be more issues than that, but I decided to search more since the post is a couple of years old. Has anyone gotten this to work?

Dennis Koch•13mo ago

Yes, I have multi-database tenancy using stancl/tenancy v4-alpha, but I guess v3 should work, too.

EleventhTower•13mo ago

@Dennis Koch that's great news. Do you remember the steps you took to get it working? I see the liverwire integration section in the docs, just wondering if there were any gotchas

Dennis Koch•13mo ago

I think I was mostly following the docs. I read it 2 or 3 times because I missed some stuff. Only gotcha was manually symlinking tenants public folders.

EleventhTower•13mo ago

Thanks for the heads up. I'll play around with this a bit later. I hadn't even looked at other laravel based packages besides Spatie

Dennis Koch•13mo ago

Most of the pain I went through was because this wasn't a fresh app, but we added tenancy later on 😅

camya•12mo ago

Hi Dennis, great that you've got it working. I am suffering with stancl/tenancy and Filament at the moment. (I use Filament Form and Table separately). In stancl/tenancy the config "asset_helper_tenancy" is set to true. - Filament styles/scripts - Loaded from the wrong folder:
"@FilamentStyles and @FilamentScripts load files from the /tenancy/ folder, which does not work. (e.g. "/tenancy/assets/js/filament/support/async-alpine.js?v=3.2.80.0") - If I set asset_helper_tenancy = false it works. - FileUpload: File uploads are not saved to the subfolder of the tenancy folder (e.g. /storage/tenantsport/), so preview does not work. The tenancy folder (public disk) is set by stancl/tenancy to /Development/valet/laravel-sites/filament-demo/storage/tenantsport/app/public/, but files are saved to /Development/valet/laravel-sites/filament-demo/storage/app/public/ by the Filament FileUpload. It looks like Filament is not using the filesystems.disks.public.root configuration value when saving the file. I hope you can give me some ideas on how to make it work. Are there changes in v4-alpha, which makes it more easy to use stancl/tenancy and Filament together?

Dennis Koch•12mo ago

Are there changes in v4-alpha, which makes it more easy to use stancl/tenancy and Filament together?

They have public folder linking now, but it didn't work in ma case so I linked them manually 😅

Filament styles/scripts - Loaded from the wrong folder:

I think you need to disable the asset_helper_tenancy.

File uploads are not saved to the subfolder of the tenancy folder (e.g. /storage/tenantsport/), so preview does not work.

Did you set the Tenant middleware for the Livewire update route?

Chris•12mo ago

I am just curious the reasons for multiple databases with multi tenancy? Is it a requirement to just have data separate or are there other benefits?

camya•12mo ago

@Dennis Koch Great tips. I used the two links below to set up "tenancy for laravel". I still have a problem with the preview url in my Filament Form. The uploaded files are correctly saved in the folder /Development/valet/laravel-sites/filament-demo/storage/tenantsport/post/01HY2S9NP685FD3TFBCXRAF7RF.png. Great. The problem is that the preview in Filament is still loading from https://sport.my-site.test/storage/post/01HY2S9NP685FD3TFBCXRAF7RF.png when it should be https://sport.my-site.test/storage/tenantsport/post/01HY2S9NP685FD3TFBCXRAF7RF.png. Do you have any idea what I am missing here? Tenancy for Laravel - Livewire: https://tenancyforlaravel.com/docs/v3/integrations/livewire/#livewire Tenancy for Laravel - Universal Routes: https://tenancyforlaravel.com/docs/v3/features/universal-routes

Dennis Koch•12mo ago

The problem is that the preview in Filament is still loading from

Did you configure your public disk in the tenancy.public config? Can you share that config? In v4-alpha it's called tenancy.filesystem.url_override. Maybe that was introduced with v4

camya•12mo ago

These are my settings. Still using the v3.8.3 of stancl/tenancy.

'filesystem' => [
    'suffix_base' => 'tenant',
    'disks' => [
        'local',
        'public',
    ],
    'root_override' => [
        'local' => '%storage_path%/app/',
        'public' => '%storage_path%/app/public/',
    ],
    'suffix_storage_path' => true,
    'asset_helper_tenancy' => false,
],

Dennis Koch•12mo ago

I guess there wasn't an option for that in v3 then.

camya•12mo ago

Hm, I have to wait for the v4 release than. Looks like symlinking the storage/tenant folders is also a challenge in v3. artisan storage:link does not work out of the box. Also this needs the tenancy.filesystem.url_override parameter too in order to set the correct url, i guess.

Dennis Koch•12mo ago

artisan storage:link only does the central public folder. You can just manually symlink the others. That shouldn't be an issue.

camya•12mo ago

I made it work kind of. Works for a first test. Ideas to optimize it are welcome. Tenant assets are now public available on https://sport.my-site.test/tenant/post/123.png I create the folders & public symlinks in CreateFrameworkDirectoriesForTenant

# config/tenancy.php
'filesystem' => [
    'suffix_base' => 'tenant/',
]

# config/tenancy.php
'filesystem' => [
    'suffix_base' => 'tenant/',
]

<?php

namespace App\Jobs;

class CreateFrameworkDirectoriesForTenant
{
    protected $tenant;

    public function __construct(Tenant $tenant)
    {
        $this->tenant = $tenant;
    }

        public function handle()
    {
        $this->tenant->run(function ($tenant) {
            $storage_path = storage_path();

            $suffixBase = config('tenancy.filesystem.suffix_base');

            if (!is_dir(public_path($suffixBase))) {
                @mkdir(public_path($suffixBase), 0777, true);
            }

            if (!is_dir($storage_path)) {
                @mkdir("{$storage_path}/app/public", 0777, true);
                @mkdir("{$storage_path}/framework/cache", 0777, true);

                symlink("{$storage_path}/app/public", public_path("{$suffixBase}{$tenant->id}"));
            }
        });
    }
}

<?php

namespace App\Jobs;

class CreateFrameworkDirectoriesForTenant
{
    protected $tenant;

    public function __construct(Tenant $tenant)
    {
        $this->tenant = $tenant;
    }

        public function handle()
    {
        $this->tenant->run(function ($tenant) {
            $storage_path = storage_path();

            $suffixBase = config('tenancy.filesystem.suffix_base');

            if (!is_dir(public_path($suffixBase))) {
                @mkdir(public_path($suffixBase), 0777, true);
            }

            if (!is_dir($storage_path)) {
                @mkdir("{$storage_path}/app/public", 0777, true);
                @mkdir("{$storage_path}/framework/cache", 0777, true);

                symlink("{$storage_path}/app/public", public_path("{$suffixBase}{$tenant->id}"));
            }
        });
    }
}

Added to...

Events\TenantCreated::class => [
    JobPipeline::make([
        CreateFrameworkDirectoriesForTenant::class,
    ])
],

Events\TenantCreated::class => [
    JobPipeline::make([
        CreateFrameworkDirectoriesForTenant::class,
    ])
],

In the custom route FileUrlMiddleware, i update the filesystems.disks.public.url config value.

use App\Http\Middleware\FileUrlMiddleware;

    ->withMiddleware(function (Middleware $middleware) {
        $middleware->group('universal', [
            FileUrlMiddleware::class
        ]);
    })

use App\Http\Middleware\FileUrlMiddleware;

    ->withMiddleware(function (Middleware $middleware) {
        $middleware->group('universal', [
            FileUrlMiddleware::class
        ]);
    })

<?php
namespace App\Http\Middleware;

class FileUrlMiddleware
{
    public function handle(Request $request, Closure $next): Response
    {
        config()->set(
            'filesystems.disks.public.url',
            url('/' . config('tenancy.filesystem.suffix_base') . tenant('id'))
        );

        return $next($request);
    }
}

<?php
namespace App\Http\Middleware;

class FileUrlMiddleware
{
    public function handle(Request $request, Closure $next): Response
    {
        config()->set(
            'filesystems.disks.public.url',
            url('/' . config('tenancy.filesystem.suffix_base') . tenant('id'))
        );

        return $next($request);
    }
}

CGM•12mo ago

Thank you @camya! I've been working on this literally all day. Your middleware idea is solid solution and was exactly what I was missing. Reading through https://discord.com/channels/883083792112300104/1180409835309764628 helped too for anyone trying to get Filament/Livewire/TenancyForLaravel working, but your solution is what solved it for me. I use a ton of different disks to keep things organized, so instead of having a single public disk I use several that I've prefixed with 'tenant' I need to refactor it, but all I have to do is just create a disk prefixed with 'tenant' and everything works with Tenancy, Filament v3 and Livewire. Of course follow the rest of the install/setup guide for tenancy regarding Livewire as well. config/filesystem.php example

 'disks' => [
  // --
  'public' => [
   'driver' => 'local',
   'root' => storage_path('app/public'),
   'url' => env('APP_URL').'/storage',
   'visibility' => 'public',
   'throw' => false,
  ],
  'tenant_logos' => [
   'driver' => 'local',
   'root' => storage_path('app/public/logos'),
   'url' => '/logos', // will be modified by FileUrlMiddleware::class
   'visibility' => 'public',
   'throw' => false,
  ],
  'tenant_photos' => [
   'driver' => 'local',
   'root' => storage_path('app/public/photos'),
   'url' => '/photos', // will be modified by FileUrlMiddleware::class
   'visibility' => 'public',
   'throw' => false,
  ],
],

 'disks' => [
  // --
  'public' => [
   'driver' => 'local',
   'root' => storage_path('app/public'),
   'url' => env('APP_URL').'/storage',
   'visibility' => 'public',
   'throw' => false,
  ],
  'tenant_logos' => [
   'driver' => 'local',
   'root' => storage_path('app/public/logos'),
   'url' => '/logos', // will be modified by FileUrlMiddleware::class
   'visibility' => 'public',
   'throw' => false,
  ],
  'tenant_photos' => [
   'driver' => 'local',
   'root' => storage_path('app/public/photos'),
   'url' => '/photos', // will be modified by FileUrlMiddleware::class
   'visibility' => 'public',
   'throw' => false,
  ],
],

then my middleware grabs each disk and applies the proper url: FileUrlMiddleware.php

class FileUrlMiddleware
{
    public function handle(Request $request, Closure $next): Response
    {
        // Get tenant-specific disks
        $tenantDisks = collect(config('filesystems.disks'))
            ->filter(fn($diskConfig, $key) => str_starts_with($key, 'tenant_'));

        // Add in any other disks that should be updated that don't start with 'tenant_'
        $disks = array_merge($tenantDisks->keys()->toArray(), ['public']);

        // Update URL configuration for each disk
        foreach ($disks as $disk) {
            $url = url('/' . config('tenancy.filesystem.suffix_base') . tenant('id') . config("filesystems.disks.$disk.url"));
            config()->set("filesystems.disks.$disk.url", $url);
        }

        return $next($request);
    }
}

class FileUrlMiddleware
{
    public function handle(Request $request, Closure $next): Response
    {
        // Get tenant-specific disks
        $tenantDisks = collect(config('filesystems.disks'))
            ->filter(fn($diskConfig, $key) => str_starts_with($key, 'tenant_'));

        // Add in any other disks that should be updated that don't start with 'tenant_'
        $disks = array_merge($tenantDisks->keys()->toArray(), ['public']);

        // Update URL configuration for each disk
        foreach ($disks as $disk) {
            $url = url('/' . config('tenancy.filesystem.suffix_base') . tenant('id') . config("filesystems.disks.$disk.url"));
            config()->set("filesystems.disks.$disk.url", $url);
        }

        return $next($request);
    }
}

And finally I added this to my TenancyServiceProvider to handle adding the tenant disks to the tenancy.php config (tenancy.filesystem.root_override and tenancy.filesystem.disks) automatically based on their names. I call this method in boot() fairly after setting middleware priority.

protected function setupTenantDisks()
{
// Get all disks from the configuration and filter for tenant-specific disks
 $tenantDisks  = collect(config('filesystems.disks'))
   ->filter(fn($diskConfig,  $key)  => str_starts_with($key,  'tenant_'))
   ->map(fn($diskConfig)  =>  Str::replaceFirst('base_path() . '/storage'  '%storage_path%',  $diskConfig['root']  ??  '')  .  '/');

 // Update the tenancy configuration with the tenant disk paths
 config()->set(
   'tenancy.filesystem.root_override',
   array_merge(config('tenancy.filesystem.root_override',  []),  $tenantDisks->toArray())
 );

 // Update the tenancy configuration with the tenant disk keys
 config()->set(
   'tenancy.filesystem.disks',
   array_merge(config('tenancy.filesystem.disks',  []),  $tenantDisks->keys()->toArray())
 );
}

protected function setupTenantDisks()
{
// Get all disks from the configuration and filter for tenant-specific disks
 $tenantDisks  = collect(config('filesystems.disks'))
   ->filter(fn($diskConfig,  $key)  => str_starts_with($key,  'tenant_'))
   ->map(fn($diskConfig)  =>  Str::replaceFirst('base_path() . '/storage'  '%storage_path%',  $diskConfig['root']  ??  '')  .  '/');

 // Update the tenancy configuration with the tenant disk paths
 config()->set(
   'tenancy.filesystem.root_override',
   array_merge(config('tenancy.filesystem.root_override',  []),  $tenantDisks->toArray())
 );

 // Update the tenancy configuration with the tenant disk keys
 config()->set(
   'tenancy.filesystem.disks',
   array_merge(config('tenancy.filesystem.disks',  []),  $tenantDisks->keys()->toArray())
 );
}

Edit: Fixed a hard-coded string that was causing problems. Should be more reliable.

Gandalf•12mo ago

I might have missed something. What were the other changes you had done apart from this to have stancl/tenancy work with filament? Where exactly did you place this portion?

use App\Http\Middleware\FileUrlMiddleware;

    ->withMiddleware(function (Middleware $middleware) {
        $middleware->group('universal', [
            FileUrlMiddleware::class
        ]);
    })

use App\Http\Middleware\FileUrlMiddleware;

    ->withMiddleware(function (Middleware $middleware) {
        $middleware->group('universal', [
            FileUrlMiddleware::class
        ]);
    })

CGM•12mo ago

I used the FileUrlMiddleware in a few places. One was in my tenant.php routes.

Route::middleware([
    PreventAccessFromCentralDomains::class,
    'web',
    TenancyServiceProvider::TENANCY_IDENTIFICATION,
    ScopeSessions::class,
    \App\Http\Middleware\FileUrlMiddleware::class,
])->group(function () {
  // Routes here
}

Route::middleware([
    PreventAccessFromCentralDomains::class,
    'web',
    TenancyServiceProvider::TENANCY_IDENTIFICATION,
    ScopeSessions::class,
    \App\Http\Middleware\FileUrlMiddleware::class,
])->group(function () {
  // Routes here
}

Another was in my TenantPortalPanelProvider.php

->middleware([
   'universal',
   TenancyServiceProvider::TENANCY_IDENTIFICATION,
   PreventAccessFromCentralDomains::class,
   \App\Http\Middleware\FileUrlMiddleware::class,
])

->middleware([
   'universal',
   TenancyServiceProvider::TENANCY_IDENTIFICATION,
   PreventAccessFromCentralDomains::class,
   \App\Http\Middleware\FileUrlMiddleware::class,
])

And finally this in my TenancyServiceProvider.php

private function prepareLivewireForTenancy(): void
    {
        FilePreviewController::$middleware = ['web', 'universal', static::TENANCY_IDENTIFICATION];

        Livewire::setUpdateRoute(function ($handle) {
            return Route::post('/livewire/update', $handle)
                ->middleware(
                    'web',
                    'universal',
                    static::TENANCY_IDENTIFICATION,
                    \App\Http\Middleware\FileUrlMiddleware::class
                );
        });
    }

private function prepareLivewireForTenancy(): void
    {
        FilePreviewController::$middleware = ['web', 'universal', static::TENANCY_IDENTIFICATION];

        Livewire::setUpdateRoute(function ($handle) {
            return Route::post('/livewire/update', $handle)
                ->middleware(
                    'web',
                    'universal',
                    static::TENANCY_IDENTIFICATION,
                    \App\Http\Middleware\FileUrlMiddleware::class
                );
        });
    }

Pretty much anywhere that needs to get a proper route to the tenants version of the file URLs. I call this (method above) in my TenancyServiceProvider.php boot() method:

$this->prepareLivewireForTenancy();

$this->prepareLivewireForTenancy();

Gandalf•12mo ago

For me things were kind of working alright with just setting tenancy.asset_helper_tenancy = false as there were no tenant specific assets. Things fell apart when I had to add Import functionality.

CGM•12mo ago

What kind of import functionality are you working with? CSV, or just uploads in general?

Gandalf•12mo ago

CSV uploads using importer action

Zen Nitiruj•12mo ago

This's gonna be nice one, with complicated work.

Gandalf•12mo ago

This is weird. After making all these changes, I can see the file upload issues getting solved, as in the fopen error went away. But for some reason the import and export jobs are failing now, as those are getting posted to central database. Although the corresponding actions (import/export) are posted to tenant database. The job ultimately fails after exceeding the number of attempts supported by the corresponding database field. File Exports were working last evening, but I hadn't committed the changes, as I wanted to do it right (via tenant folder). And just like that it started working again 🥹

Gandalf•12mo ago

Seems I spoke too early. So now the import and exports jobs are working, but the export URL like <subdomain>/filament/exports/1/download?format=csv is giving me 404. And the path on disk looks a bit different. Notice filament_exports in the folder path vis-a-vis filament/exports in the URL

CGM•12mo ago

Depending on the changes you made above, you might need to modify tenancy.php config. Double check your tenancy.filesystem.suffix_base, tenancy.filesystem.disks and finally tenancy.filesystem.root_override. I try to do this in my setupTenantDisks() method above, but you can do it manually just as easily if you dont have too many disks. That's the first place I would check if tenant files are ending up in the base public directory.

Gandalf•11mo ago

Actually the files are landing correctly in the tenant specific folder, as can be seen in the screenshot above. I think somehow the /filament/exports route is looking at the wrong place, probably the root public folder instead of tenant specific public folder Looks like the filament.exports route itself is throwing 404, as in action corresponding to the route not found from inside tenant application I am unable to figure out these 404. Has anyone else faced such an issue?

Alnuaimi•6mo ago

It dose not work with me

Alnuaimi•6mo ago

see the url is not work

Alnuaimi•6mo ago

Thank you for this awesome solution! Your work is truly excellent and creative>

David Vincent•6mo ago

@CGM Many thanks for your help ! Works like a charm!

lawre17•6mo ago

Hello @everyone I have read through the topic and I see most is about Identifying the tenant by subdomains, first question are the subdomains DNS for it to work? second question has anyone worked with anyother method like using path? has any one used the spatie multitency?

Dennis Koch•6mo ago

What do you mean by „are the subdomains DNS for it“? Path or Subdomain shouldn’t matter as long as the package supports it.

lawre17•6mo ago

Like lets say my domain is example.com and I have two tenants like foo.example.com and bar.example.com. Nomally of my dns manager I have to point the domain records to my server IP. with the subdomains approach do I have to add subdomains on my DNs manager?

Dennis Koch•6mo ago

with the subdomains approach do I have to add subdomains on my DNs manager?

Sure. Either you need to add them all manually or you use a wildcard. But wildcard SSL renewal is harder and needs DNS API access

lawre17•6mo ago

Thank you. I am working on another approach I'll share it you can correct me where I am wrong using spatie multitenancy package

CGM•2mo ago

For anyone it may help, I was mostly able to remove this middleware by implementing Spatie MediaLibrary getUrl() in regards to getting things working with tenancy for Laravel and filament. https://spatie.be/docs/laravel-medialibrary/v11/advanced-usage/generating-custom-urls

<?php

namespace App\Services\MediaLibrary;

use Spatie\MediaLibrary\MediaCollections\Models\Media;
use Spatie\MediaLibrary\Support\UrlGenerator\DefaultUrlGenerator;

class TenantAwareUrlGenerator extends DefaultUrlGenerator
{
    public function getUrl(): string
    {
        $tenantSegment = 'tenant/' . tenant()->getTenantKey();
        $url = $this->getDisk()->url($this->getPathRelativeToRoot());

        return asset('/') . $tenantSegment . $this->versionUrl($url);
    }
}

<?php

namespace App\Services\MediaLibrary;

use Spatie\MediaLibrary\MediaCollections\Models\Media;
use Spatie\MediaLibrary\Support\UrlGenerator\DefaultUrlGenerator;

class TenantAwareUrlGenerator extends DefaultUrlGenerator
{
    public function getUrl(): string
    {
        $tenantSegment = 'tenant/' . tenant()->getTenantKey();
        $url = $this->getDisk()->url($this->getPathRelativeToRoot());

        return asset('/') . $tenantSegment . $this->versionUrl($url);
    }
}

Still need to properly setup tenant disks and such, but this removed my need for the FileUrlMiddleware::class. I started giving me trouble on something I was working on so refactored to this. If you still use other field types you might still need the middleware, but I've just started using media library for everything at this point.

Alnuaimi•2mo ago

Hi, Ok ,good solution,but any user can acess file without auth How secure it please help me

Dennis Koch•2mo ago

Put a middleware in front

Alnuaimi•2mo ago

which middleware?

Dennis Koch•2mo ago

The one that does what you want 😅 If you just want to Authenticate the user, use Authenticate. If you need to check permissions, use an additional Policy.

Alnuaimi•2mo ago

Thank you for your comment! I understand that you're suggesting using Authenticate for user verification and Policy for permission checks. In my case, the issue isn't with authentication or permissions, but rather with how to display files stored on the local disk (local disk) in the form. I’m using a Multi-Tenancy system, and the files are being stored correctly in each tenant's designated folders. However, when trying to display the file in the form, it doesn’t show up properly. I believe the issue might be with the file paths or how they’re being accessed. If you have any experience dealing with such cases, I’d be grateful to hear your suggestions! 😊

Dennis Koch•2mo ago

You posted this, which reads like a permission issue:

but any user can acess file without auth

I believe the issue might be with the file paths or how they’re being accessed.

Did you debug this? What's the file path that's loaded? What's the actual file? Is it the public disk?

awcodes•2mo ago

Files on any private disk are not accessible publicly so to make them viewable, downloadable etc has to go through a url that you set up to serve them that can check the authentication / authorization to return them as an image etc. Basically, you have to serve them through a proxy url if they are stored locally as private.

Dhru•2mo ago

So basically if OP uses something like aws and temp urls that should work right ?

Alnuaimi•2mo ago

look ,I want to use local disk with tenancyforlaravel ,every thing is ok but no display in form you can check my config

Alnuaimi•2mo ago

awcodes•2mo ago

Local disk is not publicly accessible via a url, which is what image tags need to display them so have to set up a proxy url to serve them through that can validate if the user can see them. You wouldn’t want tenants to be able to view each others files.

Alnuaimi•2mo ago

yes ,this is important but before how to fix with local disk this is middleware for public you can look <?php namespace App\Http\Middleware; use Illuminate\Http\Request; use Closure; class FileUrlMiddleware { public function handle(Request $request, Closure $next) { config()->set( 'filesystems.disks.public.url', url('/' . config('tenancy.filesystem.suffix_base') . tenant('id')) );
return $next($request); } }

awcodes•2mo ago

Ok, but the local disk where your images are getting stored aren’t in the directory associated with the public url. And there’s no symlink to them in the public directory therefore they can’t be served out. That’s why you need a proxy url setup in your routes file to verify everything and return the file as the appropriate response.

Alnuaimi•2mo ago

File::link("{$storage_path}/app/public", public_path("{$suffixBase}{$tenant->id}")); you mean that ?

awcodes•2mo ago

Yea, but the local directory isn’t in public_path. It’s in storage_path() There’s plenty of articles about serving private files with laravel. Just do a quick google search and read some of them. It’s hard to explain through here. Sorry.

Dennis Koch•2mo ago

You need this: https://laravel.com/docs/master/filesystem#customizing-temporary-urls plus a controller that serves your files

File Storage - Laravel Upcoming - The PHP Framework For Web Artisans

Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.

Gaming

Programming

Multi tenancy with multiple database support

Did you find this page helpful?