Skip to content

Latest commit

 

History

History
50 lines (33 loc) · 2.56 KB

inbound-proxies.md

File metadata and controls

50 lines (33 loc) · 2.56 KB

Inbound Proxies

Why

We need to expose our applications on www.telus.com!

What

We have a proprietary nginx-based inbound proxy, which routes ALL requests to TELUS digital assets.

How

We present www.telus.com and a few subdomains used to route to application environments:

Develop, test, staging

To have traffic from http://www.wctest.telus.com/en/bc/foo/bar proxied to your application, you need to:

  1. fork https://github.com/telusdigital/inbound.telus-gateway-staging-config
  2. create nginx rule(s) that matches the traffic you're wanting to serve, and proxies them to where your application is hosted
  3. create tests confirming that traffic is matched and proxies correctly example
  4. Run the tests locally (README)
  5. Commit your changes to a branch that contains the Jira Issue Stub, ie BMK-560
  6. Submit a pull request. If your request needs merging at a specific time, please note that in your pull request.
  7. Request for this change to be merged in #g-delivery. If you've added a route, but have no tests, it won't be merged.

Production

To have traffic from http://www.telus.com/en/bc/foo/bar proxied to your application, you need to:

  1. fork https://github.com/telusdigital/inbound.telus-gateway-production-config
  2. create nginx rule(s) that matches the traffic you're wanting to serve, and proxies them to where your application is hosted
  3. create tests confirming that traffic is matched and proxies correctly example
  4. Run the tests locally (README)
  5. Commit your changes to a branch that contains the Jira Issue Stub, ie BMK-560
  6. Submit a pull request. If your request needs merging at a specific time, please note that in your pull request.
  7. Request for this change to be merged in #g-delivery.

Who

@delivery

References