Route helper in job doesn't use tenant context domain

[giorgiopogliani]

Route helper in job doesn't use tenant context domain

[stancl]

This isn't done by the package automatically because there's no way for the package to know what the correct domain is:

• tenants can have multiple (sub)domains
• there may be multiple central domains

You should manually update app.url or use app('url')->forceRoot() with the right hostname.

We've added a bootstrapper for this in v4 but it still requires configuration due to the reasons above.

[giorgiopogliani]

Could we add a primary domain config somewhere, maybe as extra column in the domains table?

[stancl]

Yes, you can do that. It's up to you how you approach this, the right solution here will be application-specific.

[giorgiopogliani]

Ok, might be a common use case, anyway I'll handle it. Thanks for the super fast reply!

[stancl]

In v4 we've added:

• default configuration for the new bootstrapper that just uses domains->first() iirc
• single domain tenants, for cases where you might not need a separate domains table. So the domain is just stored on a string column

In the SaaS boilerplate we use this primary domain concept. iirc it's a hasOne() relation from the tenant.

The package won't ship with primary domains out of the box since they only make sense when you really do need multiple domains and have some UI for letting the tenant manage their domains. But the changes we've made should add a good default implementation for this use case.