Skip to content
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

Distinct server names or routes to applications on UAT #1724

Closed
pgwillia opened this issue Jun 18, 2020 · 3 comments · Fixed by #1861
Closed

Distinct server names or routes to applications on UAT #1724

pgwillia opened this issue Jun 18, 2020 · 3 comments · Fixed by #1861

Comments

@pgwillia
Copy link
Member

pgwillia commented Jun 18, 2020

Distinct server names or routes to applications instead of port ‘x’ is Jupiter, port ‘y’ is avalon, etc. Personally, I find names easier to remember than numbers. If the applications are containerised, a reverse proxy could handle the routing. Envoy or Traefik?

Originally posted by @pgwillia in #1680 (comment)

@pgwillia
Copy link
Member Author

pgwillia commented Jul 9, 2020

nginx-proxy looks to be another option. It can handle multiple virtual hosts and has thought about SSL using let's encrypt. There's an example for what this could look like as a docker-compose

@pgwillia
Copy link
Member Author

pgwillia commented Jul 9, 2020

Here's an article which describes Traefik where you add Traefik labels

version: "3"services:
  calibre:
    image: linuxserver/calibre-web
    container_name: calibre
    restart: unless-stopped
    ports:
      - "9083:8083"
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.cal.rule=Host(`books.mydomain.com`)"
      - "traefik.http.routers.cal.entrypoints=web"
      - "traefik.http.services.cal.loadbalancer.server.port=9083"

@pgwillia
Copy link
Member Author

Wendy added a wildcard dns entry of *.uat.library.ualberta.ca will resolve to uat.serv01.library.ualberta.ca.

https://kb.porkbun.com/article/94-what-is-a-wildcard-dns-record#:~:text=A%20wildcard%20DNS%20record%20is,(*)%20in%20the%20host%20field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant