Hi @iskurbanov I’m following your guide on implementing a multi-tenant architecture for one of our existing products. However, we have a situation where our client already has separate hosting for domain.com and app.domain.com. Could you let me know if using wildcard subdomains might interfere with these existing domains? Thanks!
Same question here, I've also implemented a multi-tenant app with i18n next-intl and it works but I still facing some conflict problems in the app structure, cuz I need to set up localization for the dashboard and landing page only without affecting the dynamic route like [domain]
I've implemented analagous logic with the App dir and it's working perfectly well! If fact your file structure in the App dir will look exactly the same, just create the "site" logic in a page.tsx file instead of index.tsx.
I also added the following to route both my domain and localhost to another folder such that I could work with that instead of the root domain defualting to the DEFAULT_HOST like in this tutorial. Helped with running locally and debugging!
Hi @iskurbanov
I’m following your guide on implementing a multi-tenant architecture for one of our existing products. However, we have a situation where our client already has separate hosting for domain.com and app.domain.com. Could you let me know if using wildcard subdomains might interfere with these existing domains?
Thanks!
My challenge is to host this with AWS rather than Vercel
Thanks, @iskurbanov , this post helps me a lot.
I have a multi-tenancy SSG app, how can I add i18n? Can you give me some advice?
Same question here, I've also implemented a multi-tenant app with i18n
next-intl
and it works but I still facing some conflict problems in the app structure, cuz I need to set up localization for the dashboard and landing page only without affecting the dynamic route like[domain]
Would it be possible for customers to bring their own custom domain instead of the wildcard ?
Yes of course, checkout the Next.js platform starter kit for example of using custom domains: vercel.com/templates/next.js/platf...
Great article !
Do you have any idea on how to set up environnement variable for each sub-site ?
Thanks !
Will adding a prefix help?
For example key is
domain:key
couple of questions
I've implemented analagous logic with the App dir and it's working perfectly well! If fact your file structure in the App dir will look exactly the same, just create the "site" logic in a
page.tsx
file instead ofindex.tsx
.I also added the following to route both my domain and localhost to another folder such that I could work with that instead of the root domain defualting to the
DEFAULT_HOST
like in this tutorial. Helped with running locally and debugging!This is cool. Can u explain how can i using multitenancy and pathname both?
e.g.: user1.hosted-url.com/about
Thanks before
Same logic :)
Add the following logic for user1.hosted-url.com/about