Custom Domains for Territories #1958
Draft
+389
−7
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.
Description
Tracks the work and strategies for #1942
Adds custom domains for territories with automatic and one-click sign-in.
TBD
Screenshots
tbd
Additional Context
Subject to updates
WIP: Shared Authentication
Login is based on referer, signup redirects to stacker.news
Note: This is at the moment unsafe and only a proof of concept
Login
User goes directly to forum.pizza.com (no referer)
-- TODO: One-click sign in: If the user is already logged in on stacker.news, transfer the auth cookies
User visits forum.pizza.com from stacker.news (referer)
-- WIP: Automagical redirect with auth cookies from stacker.news
TODO: Signup
The user gets redirected to stacker.news to signup and gets redirected back with the auth cookies
TODO: Saving custom domains
cachedFetcher will fetch and cache for 5 minutes the list of domains that are
VERIFIED
TODO: Serve subdomains for CNAMEs
We can create record on-demand via Route 53 APIs, though this needs to be researched more.
TODO: Automatic SSL certificates
AWS Certificate Manager can be controlled with their API to provide ssl certificates on-demand
TODO: DNS guide on FAQ
FAQ to most populars domain providers. The territory owner will have to set a CNAME and that's it.
A TXT record can be used to validate domain ownership
Checklist
Are your changes backwards compatible? Please answer below:
tbd
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
tbd
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
tbd
Did you introduce any new environment variables? If so, call them out explicitly here:
tbd
Progress
Subject to updates
Personalization
SSL
DNS
Territory Edit
-- Custom Domains relation handling via resolver
Domains
Navigation
Middleware
Auth Sync