I want to build an array of sites using sanity. I want to be able to create, customize, deploy and assign domain these sites from the CMS i.e. by non technical people. I found this documentation https://vercel.com/guides/nextjs-multi-tenant-application
Is there a way to do this? Is it mandatory to create one vercel project and repo per site?
Yes, you can absolutely build this! You don't need to create one Vercel project and repo per site. Instead, you can use Vercel's multi-tenant architecture with a single Next.js application that serves multiple sites dynamically based on the domain 1.
How Multi-Tenant Architecture Works
With Vercel's multi-tenant approach, you have:
- One codebase (Next.js app)
- One Vercel deployment
- Multiple domains pointing to the same deployment
- Dynamic content served based on the requesting domain
Each tenant gets their own domain or subdomain, but you only have one Next.js deployment running on Vercel 1.
Architecture Overview
Here's how you can structure this with Sanity:
Key Benefits
- Single Codebase: One Next.js app serves all sites
- Dynamic Content: Content is fetched from Sanity based on the requesting domain
- Automatic SSL: Vercel handles SSL certificates for all domains 1
- Scalable: Can handle thousands of sites from one deployment
- Cost Effective: No need for multiple deployments
Domain Management
Subdomains
For subdomains like tenant1.yourdomain.com, add a wildcard domain *.yourdomain.com to your Vercel project 1.
Custom Domains
For custom domains, you can programmatically add them using the Vercel API as shown in the code above 1.
Sanity CMS Integration
Your Sanity schema would include:
- Sites: Each with domain configuration, theme settings, and content
- Pages: Individual pages for each site
- Components: Reusable content blocks
- Themes: Color schemes, fonts, layouts
Non-technical users can:
- Create new sites through Sanity Studio
- Customize themes and content
- Add custom domains
- Manage all sites from one interface
This approach gives you the flexibility of a multi-tenant architecture while maintaining the simplicity of a single codebase and deployment.
To configure the generation, complete these steps:
The code returns the following error:
Configuration must contain `projectId`
at et (@sanity/client)
at r.config (@sanity/client)
at new r (@sanity/client)
at createClient (@sanity/client)
at (/lib/sanity)
Revise the code to address the error.
I was previewing: /
I'll fix the Sanity client configuration error by adding the required projectId and other necessary configuration options.
The error was occurring because the Sanity client requires a projectId to connect to your Sanity project. Here's what I've fixed:
- Added required configuration: The Sanity client now includes
projectId,dataset,useCdn, andapiVersion - Environment variables: Added environment variables for the Sanity configuration
- Fallback values: Included fallback values in case environment variables aren't set
To complete the setup:
Get your Sanity Project ID:
- Go to your Sanity dashboard at sanity.io
- Find your project ID in the project settings
- Replace
your-sanity-project-idin the.env.localfile
Set up your dataset:
- Most projects use
productionas the dataset name - Update if you're using a different dataset name
- Most projects use
Add a Sanity token (if you need write access):
- Generate a token in your Sanity project settings
- Add it to the environment variables
The configuration should now work without the projectId error.
To configure the generation, complete these steps: