Add support for regex host and priority for domain
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I am trying to deploy Zrok which create custom host on the fly like ******.share.example.com using docker compose.
Describe the solution you'd like
Add the possibility for specifying if the host must be regexed and the priority when creating the domain. For example in my case:
zrok.share.example.com -> zrok-controller:18080 with priority 1
*.share.example.com -> zrok-frontend:80 with priority 100
Describe alternatives you've considered
I have tried to update the traefik directory without success
Additional context
No response
Will you send a PR to implement it?
Yes
Contributor guide
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 inspecting the traefik directory and the Docker Compose domain configuration, focusing on how hosts are created and routed. Implement regex host matching and configurable priority so the specific zrok host can take priority 1 and the wildcard host priority 100, then verify both routing examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100