Skip to content
New issue

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

Multi-site per tenant should be set by the tenants' superadmins, not by developers #1

Open
hazho opened this issue May 3, 2022 · 2 comments

Comments

@hazho
Copy link

hazho commented May 3, 2022

currently, tenant superuser can create another site for themselves, but the tenant middleware is preventing them from visiting it, because there is no tenant-record for the newly created site domain, even if it is a sub-domain..!
it would be great if we automate the tenant-record registering for the multi-sites per tenant/ without the need to create a new schema..!

@borisbrue
Copy link
Owner

Hi @hazho thanks for your input! I dont know if this is possible with the underlying approach. But feel free to provide something we can use.

I did not ran into the issue because i used TLDs for the hostnames and wagtail as a headless_cms. internally all route to an personalized wagtail router which checks the hostname and provides the correct site data. I could share the code if thats something you would like to try

@hazho
Copy link
Author

hazho commented May 14, 2022

I was worriyng the same, please share what related, it may help me and others

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants