Custom Domain Bindings
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
How would this look if we were to add custom domains following this guide: https://vercel.com/guides/nextjs-multi-tenant-application
Would we have to change the middleware to check the full domain or is there some other recommendation?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing middleware entry point and the linked Next.js multi-tenant guide to understand how custom domains would fit this project. The issue needs a decided recommendation and defined implementation scope before completion can be assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100