Google App Engine API +静态架构(Google App Engine API + static architecture)

 我正在尝试（构建）构建JS客户端+ NodeJS服务器应用程序以在Google Cloud AppEngine（以及可能的其他GCP资源）上托管它的最佳方法。 所以我在这里寻找建议/最佳实践。 
 
 我们有一个在非默认AppEngine服务上运行的API服务器，并且希望能够在同一个项目上运行多个（例如开发/暂存/生产版本）（如果可能）。 
 
 我们希望在此系统上托管/提供我们的静态客户端应用程序，因为我们希望使用相同的域来指向它。 
 
 在我们基于服务器的常规设置中，客户端应用程序在domain.com/上代理/提供，对API的请求在domain.com/v1/ 
 
 我一直在研究不同的选项 - 在AppEngine上运行一个单独的静态站点，并使用dispatch.yaml尝试路由请求 - 这个选项似乎不适用于域前缀，只有通配符，例如 
 
dispatch:
- url: "my-client-service-project.appspot.com/"
  service: my-client-service
- url: "my-client-service-project.appspot.com/v1/*"
  service: my-backend-service
 
 不起作用，但是： 
 
- url: "*/v1/*"
  service: my-backend-service
 
 是的，我们不想要的，因为我们想要尽可能地运行dev ， staging和production 。 
 
 我一直在看的另一个选项是将静态文件夹作为我的应用程序的一部分托管，但我似乎无法使其工作，这里是我的app.yaml的片段： 
 
handlers:
  - url: /.*
    static_files: client/dist/index.html
    upload: frontend/dist/index.html
  - url: /v1/*
    script: dist/index.js
 
 我的猜测是script可能与Python应用程序的工作方式不同，但我可能错了 - 文档不是很清楚。 
 
 理想情况下，我想在存储上托管客户端前端静态文件并指向AppEngine API服务器（没有专门指向客户端的域，例如/v1/auth/login而不是my-backend-service-project.appspot.com/v1/ 
 
 参考文献： 
 
 如何在google flex / app引擎环境中使用存储桶存储来提供静态文件？ 
 
 由Google App Engine提供的Node.js +静态内容 
 
 https://cloud.google.com/appengine/docs/flexible/nodejs/serving-static-files 
 
 https://cloud.google.com/appengine/docs/standard/python/how-requests-are-routed#routing_via_url 
 
 https://cloud.google.com/appengine/docs/standard/python/config/appref 
 
 https://cloud.google.com/appengine/docs/standard/python/config/dispatchref 

I'm trying to (con)figure the best way to structure a JS client + NodeJS server app to host it on Google Cloud AppEngine (plus possibly other GCP resources). So I'm looking for advice / best practices here.
 
We have an API server running on a non-default AppEngine service and would like to be able to run several, e.g. development/staging/production versions on the same project (if possible).
 
We would like to host / serve our static client app on this system because we want to use the same domain to point at it.
 
In our normal server based setup, the client app is proxied/served on domain.com/ and requests to the API are on domain.com/v1/
 
I've been working through different options - hosting a separate static site running on AppEngine and using dispatch.yaml to try to route requests - this option doesn't seem to work with domain prefixes, only wildcards, e.g.
 
dispatch:
- url: "my-client-service-project.appspot.com/"
  service: my-client-service
- url: "my-client-service-project.appspot.com/v1/*"
  service: my-backend-service
 
Doesn't work, but:
 
- url: "*/v1/*"
  service: my-backend-service
 
Does, which we didn't want because we'd like to run dev, staging & production if possible.
 
The other option I've been looking at is having the static folder hosted as part of my app, but I can't seem to get this working either, here is the snippet from my app.yaml:
 
handlers:
  - url: /.*
    static_files: client/dist/index.html
    upload: frontend/dist/index.html
  - url: /v1/*
    script: dist/index.js
 
My guess is that script may not work the same as for Python apps, but I could be wrong - the doc's aren't very clear.
 
Ideally, I'd like to host the client front-end static files on storage and point to the AppEngine API server (without specifically pointing to a domain from the client, e.g. /v1/auth/login rather than my-backend-service-project.appspot.com/v1/
 
References:
 
How can I use bucket storage to serve static files on google flex/app engine environment?
 
Node.js + static content served by Google App Engine
 
https://cloud.google.com/appengine/docs/flexible/nodejs/serving-static-files
 
https://cloud.google.com/appengine/docs/standard/python/how-requests-are-routed#routing_via_url
 
https://cloud.google.com/appengine/docs/standard/python/config/appref
 
https://cloud.google.com/appengine/docs/standard/python/config/dispatchref

原文：https://stackoverflow.com/questions/48705676