Closed Bug 1294371 Opened 8 years ago Closed 8 years ago

Handle multiple custom domain names

Categories

(Participation Infrastructure :: Community Ops, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: yousef, Assigned: yousef)

References

Details

Right now we can map one domain name to a service but sometimes we need more. There's two ways we could do this:

Redirect all www to non-www: Covers the main use-case for this but the regex might slow requests down slightly?

Expand template: Use a folder in the Consul k/v and loop over them in consul-template
Blocks: 1293796
Assignee: nobody → yousef
Status: NEW → ASSIGNED
So we're going to go with a mix of both here and have a global redirect folder in consul, which can handle all non-cname use cases.

Plan is to:
- Create Consul k/v folder and populate it
- Change the haproxy template to loop over the keys in the folder and redirect to the value
Blocks: 1297147
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.