ct-Open-Source / ct-Open-Source/team-container
How to use subdirectories instead of subdomains?
- Dominant language
- HTML
- Stars
- 116
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Instead of using subdomains (video.example.org, chat.example.org; cloud.example.org and www.example.org) I would prefer subdirs (www.example.org/video, www.example.org/chat, www.example.org/cloud). That seems for me clearer and more obvious. Furthermore https://spdyn.de/ is limiting the number of subdomains to 5. And ... it didn't work for me...
So can someone give me a hint (example) which parameters are to be set in the *.yaml to organize the team-container with subdirs?
Thanks a lot!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the *.yaml parameters that configure the team-container services and reviewing how their current subdomain routing is defined. Determine whether those settings can represent paths such as /video, /chat, and /cloud, then document or demonstrate the configuration needed for subdirectory-based access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100