Run multiple websites using the same Laravel installation while keeping tenant specific data separated for fully independent multi-domain setups, previously github.com/hyn/multi-tenant
I have a website which is using this tenancy plugins, the portal can accessible both by user and by internal process,
the internal process covered with VPN IP address, the user will be using FQDN, in this case I register VPN IP as a new tenant, then FQDN as a new tenant.
Proposed behavior
What I expect is the VPN IP tenant should have destination same as FQDN tenant, same storage (as an ALIAS) instead of working in different tenant
Current behavior
VPN IP tenant and FQDN tenant is two different thing which is not related each other
Description of your feature
I have a website which is using this tenancy plugins, the portal can accessible both by user and by internal process, the internal process covered with VPN IP address, the user will be using FQDN, in this case I register VPN IP as a new tenant, then FQDN as a new tenant.
Proposed behavior
What I expect is the VPN IP tenant should have destination same as FQDN tenant, same storage (as an ALIAS) instead of working in different tenant
Current behavior
VPN IP tenant and FQDN tenant is two different thing which is not related each other
Information