Context Navigation

Changes between Version 1 and Version 2 of Ticket #234, comment 5

v1	v2
5	5	The complicated part is how users "claim" subdomains, or other domains that are user-specific. for example, nel has `endofthe.world` that she wants to be hosted at devhack but doesn't want to give other users access to. Do we specify this in the same place as our more permanent domain mappings?? or my claim of `m.devhack.fun`.
6	6
7		Obviously these mappings need to be specified __somewhere__. whether kubernetes CRDs, zone files / nameservers, a database / key value store like postgres or redis, or merely unix directory perms. Subdomain routing could exist, as could a fallback routing. And then wherever it gets specified it gets translated to traefik routing (but traefik assumes a total list of all domains being served (for https at least)).
	7	Obviously these mappings need to be specified __somewhere__. whether kubernetes CRDs, zone files / nameservers, a database / key value store like postgres or redis, or merely unix directory perms. Subdomain wildcard dynamic routing could exist, as could a fallback routing. And then wherever it gets specified it gets translated to traefik routing (but traefik assumes a total list of all domains being served (for https at least)). Caddy allows doing wildcard https routing, it requests certificates as soon as the domain name is hit.