We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using Laravel Octane with the TenantConfig feature enabled, the configuration is always from the previous request
When visiting tenant a, tenant a should appear, and the same for tenant b.
The text was updated successfully, but these errors were encountered:
Octane isn't officially supported yet, I'll be focusing on that in v4.
Sorry, something went wrong.
Found this thread on google, very happy using this package in our application, keep up the good work. I hope octane support comes too 👍 👍
stancl
No branches or pull requests
Describe the bug
When using Laravel Octane with the TenantConfig feature enabled, the configuration is always from the previous request
Steps to reproduce
Expected behavior
When visiting tenant a, tenant a should appear, and the same for tenant b.
Your setup
The text was updated successfully, but these errors were encountered: