Basset not work for multi-tenancy structure

[ben-cheng565]

In a multi-tenancy project, I recently upgraded the backpack to v6, but I have no idea how to configure APP_URL in env file. Since each tenant has a different URL, so packages cannot be loaded using basset.

[backpack-ai-bot[bot]]

🚨 Bot is not sure about this answer. Please verify. 🚨

Based on the information provided in the knowledge sources, I don't have a specific solution for configuring Basset in a multi-tenancy structure with Backpack v6. However, I can offer some insights and suggestions:

1. Basset relies heavily on the APP_URL setting in the .env file for asset loading Github Issue 5127. This can be problematic in a multi-tenancy setup where each tenant has a different URL.

2. There isn't a direct solution mentioned for multi-tenancy in the provided knowledge sources. However, one user asked about implementing Backpack with multi-tenancy, and a suggestion was made to look into Spatie's Laravel Multi-tenancy package Community Forum Discussion 310.

3. You might need to explore custom solutions or modifications to Basset to handle multiple URLs. One possible approach could be dynamically setting the APP_URL based on the current tenant, but this would require careful implementation and testing.

4. It's worth noting that Backpack's asset loading mechanism has changed significantly in v6 with the introduction of Basset Github Issue 5048, which might complicate multi-tenancy setups that worked with previous versions.

Given the complexity of this issue and the lack of direct information about multi-tenancy support in Backpack v6 with Basset, I would recommend:

1. Reaching out to the Backpack community or creating a new issue on their GitHub repository to ask for guidance on this specific use case.
2. Exploring if there are any workarounds or custom solutions that can be implemented to handle asset loading for multiple tenants.
3. Considering the use of a dedicated multi-tenancy package like Spatie's, as suggested in the community forum, and seeing if it can be integrated with Backpack v6 and Basset.

Remember to thoroughly test any solution you implement, as asset loading is crucial for the proper functioning of the Backpack admin panel.

Relevant sources:

Github Issue (closed): [Bug] Backpack Assets 404 if APP_URL is set and doesn't match to actual URL
Github Issue (closed): [Bug] Basset check error on backpack:install - docker composer
Github Issue (closed): [Bug] standard backpack install doesn't load css files properly
Github Issue (closed): [HAS-FIX] ASSETS NOT LOADING FROM CDNS - 12-04-2024
Github Issue (closed): Backpack v6 assets path issue
Backpack in a subdomain
Github Issue (closed): [Bug] No hint path defined for [backpack].
Github Issue (closed): [Bug]
Bug report
Github Issue (closed): [Bug] nestedSortable is not a function
Github Issue (closed): Remove backpack:publish-assets command from v6
Github Issue (closed): 3 issues
is there anyone tried backpack with multitenant implementation ?
Github Issue (closed): [Bug] CSS not loaded when pushed on production

[siberfx]

could you please share some pieces of your tenancy system about? so I can try to help you with that

[ben-cheng565]

Thanks. My project uses stancl/tenancy for multi-tenancy management, and the APP_URL in .env file has a value as the base URL, then each tenant has a dynamic URL generated from APP_URL, (https://subdomain.APP_URL).
After upgrading Backpack to 6, which utilizes Basset to load resources, but Basset requires a fixed APP_URL, each backpack page cannot get resource files, as shown in the screenshot below.

I have got a solution from https://github.com/Laravel-Backpack/basset/issues/139#issuecomment-2374368512https://github.com/Laravel-Backpack/basset/issues/139#issuecomment-2374368512

[karandatwani92]

Hey @ben-cheng565 How are you?

Can you share the solution that worked for you?
Some code and steps would help me write the tutorial on this and help others. Thanks 🙏

[ben-cheng565]

Hey @karandatwani92 , I am glad to share it to help others with a similar case.

Step 1, Run the command to generate the basset config file if it does not exist
php artisan vendor:publish --provider="Backpack\Basset\BassetServiceProvider"
Then change 'disk' => env('BASSET_DISK', 'public') to 'disk' => env('BASSET_DISK', 'basset')

Step 2, Add basset to the disks array in the filesystems.php

        'basset' => [
            'driver' => 'local',
            'root' => storage_path('app/public'),
            'url' => '/storage',      # set url without prefix for the case that central app has a different URL
            'visibility' => 'public',
            'throw' => false,
        ],

Step 3, Modify AppServiceProvider file to reset the disk link for tenants:

public function boot()
    {
        Event::listen(TenancyBootstrapped::class, function (TenancyBootstrapped $event) {
            # Your code here
            
            # Reset the basset disk link to the tenant's storage
            config()->set('backpack.basset.disk', 'basset');
            config()->set('filesystems.disks.basset.url', asset('storage'));
            app()->scoped('basset', fn() => new \Backpack\Basset\BassetManager());
        });

[jcastroa87]

Thanks @ben-cheng565 for sharing this information.

I will close the issue, but please feel free to re-open or create a new one if needed.

Cheers.