Vytautas Smilingis
Vytautas Smilingis
@RaazPuspa are the routes working when you visit them manually in your browser? If so then this might be an issue of routes being registered once on boot. Try calling...
Would you be able to share the cron job and how you are calling it?
Just to confirm it, could you try booting the route provider after identifying the tenant and then immediately try to resolve the route?
I suggest looking into Laravel `storage:link` command: https://github.com/laravel/framework/blob/6.x/src/Illuminate/Foundation/Console/StorageLinkCommand.php It creates a link from your storage folder to public folder. This will not solve the `tenant's images only under tenant's url`...
You can copy the vhost file from package source, edit it and specify it in webserver.php config.
I don't think there are any plans to include this driver, but you could write your own. We'd probably accept a PR that includes this.
If you could, please create a Pull Request with some tests so we're sure nothing breaks.
#781 should've fixed the issues with queue provider. 5.4.4 has been tagged.
One issue remains regarding tenant override for queueables (notifications, mail...). We're currently checking if `$website_id` property was set on the command that is being processed. Queueables work differently as it's...
After further investigation it seems that config override does work. When a tenant is identified it also overrides the config values. This issue lies with how Mail service is set...