Google Front End (GFE)
Google Front End (GFE) is reverse-proxy frontend service provided by GCP. The Core Services team operates and maintains the GFE instances that front Sourcegraph.com and various internal services.
Each GFE instance consists of two environments:
- For the QA environment, the infrastructure is defined in
sourcegraph/infrastructure/gfe/envs/qa/project - For the production environment, the infrastructure is defined in
sourcegraph/infrastructure/gfe/envs/prod/project
Two types of URL mapping semantics are currently supported:
- Exact URL match: Requests matching the exact URL will be routed to the specified backend
- Prefix URL match: Requests with a URL prefix will be routed to the specified backend. The longest matching prefix takes precedence
Sourcergaph.com
The Sourcegraph.com GFE transparently proxying traffic to Marketing site Netlify deployment, Sourcegraph Docs v2 Vercel deployment and Community Code Search deployment:
Proxy routing is based on the URL mapping (routes.tf):
- Unless explicitly matched, all traffic goes to the Community Code Search deployment by default.
- The list of
marketing_pagesspecifies exact URL matches. - The list of
marketing_foldersspecifies prefix URL matches.
Environments setup:
- For the QA environment:
- Uses https://testwww.sourcegraph.com to access the GFE
- URL mapping is defined in the
envs/qa/project/routes.tf
- For the production environment:
- Uses https://newwww.sourcegraph.com to access the GFE (for the time being, this will transition to just sourcegraph.com by mid-Dec, 2023)
- URL mapping is defined in the
envs/prod/project/routes.tf