How gaowanlu/google works
This is a small Next.js site whose documented purpose is to expose a configurable upstream website through a Vercel-hosted proxy. The main runtime path is an incoming browser request, the proxy handler, and the configured upstream. The README also documents domain/DNS setup and Vercel deployment; the supplied source does not show their configuration internals. The homepage appears to be a separate placeholder UI.
Main entry points: proxy.js Proxy handler · _app.js App shell · index.js Homepage
Components 9
Proxy runtime
- Proxy handler
api/proxy.js - Configured upstream
Hosting setup
- Vercel hosting
- Domain DNS
Other components
- Browser
- Domain administrator
Connections 11
- Browser → Vercel hosting: requests site
- Vercel hosting → Proxy handler: invokes handler
- Proxy handler → Configured upstream: proxies request
- Configured upstream → Proxy handler: returns response
- Proxy handler → Vercel hosting: returns response
- Vercel hosting → Browser: serves response
- Domain administrator → Domain DNS: configures records
- Domain administrator → Vercel hosting: configures domain
- Domain DNS → Vercel hosting: routes domain
- Vercel hosting → App shell: serves app
- App shell → Homepage: renders page