-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wildcard behind wildcard #1
Comments
To clarify - HAProxy gives each container a random CNAME entry? like jaunty_horse.domain.com and iggy_falafel.domain.com and you need the host manager to listen on those domains when the container starts? The DOMAINALIAS setting in the run command basically just sets an environment variable, this ENV variable is then processed by a script (entrypoint.sh) which does a search and replace on the nginx configuration templates stored in the container. It's just a convenient way to do the domain configuration. You have full control over those files, look at them here You can see where the
The thing is, those files make use of subdomains as the main entrypoint and use the organisation ID (or the organisation slug) to properly identify the portal owner, so you would have To get this to work you might want something like this in the portal.conf server_name field:
That will now prepnd the If you have only one internal organisation, you could completely remove the if conditions around the
Or, if you pass the entire CNAME into the run command:
This is just an idea - lots of assumptions there :-/ but your solution definetely lies in taking control over those templates and m oulding them to your domain requirements. M. |
I'm hosting this container behind openshift (kubernetes) and so there's a wildcard DNS entry for containers through HAProxy. How would I set a wildcard CNAME for my DOMAINALIAS (which is set to the the hostname in the wildcard). I hope this makes sense.
The text was updated successfully, but these errors were encountered: