docs: add limitations section to custom domains guide#39385
Merged
johnstonmatt merged 3 commits intomasterfrom Oct 9, 2025
Merged
docs: add limitations section to custom domains guide#39385johnstonmatt merged 3 commits intomasterfrom
johnstonmatt merged 3 commits intomasterfrom
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ChrisChinchilla
requested changes
Oct 9, 2025
ivasilov
pushed a commit
that referenced
this pull request
Oct 14, 2025
* docs: add limitations section to custom domains guide * docs: remove note on cost of custom domains
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
docs content: adds notes about the limitations of custom domains on the platform
What is the current behavior?
The custom domains feature did not meet my needs and I didn't find out until after enrolling.
What is the new behavior?
These changes aim to help users understand when custom domains may not be the right fit. Maybe some day soon they will be more broadly useful, but in the meantime I think adding this information in a prominent place will save users some hassle.
Additional context