Deploying containers to Google Cloud Run
To deploy our application to Google Cloud Run, there are a few changes we need to make to the packaging of our frontend.
Frontend configuration
As Google Cloud Run has no configuration available for ingress or path-based routing of HTTP(S) requests, we will need to implement the reverse proxy approach to the Strangler Façade pattern. The following default.conf configuration file declares how the various URL paths will be handled:
server {
listen 80;
server_name app.banking.jasonmarston.me.uk;
location / {
root /usr/share/nginx/html;
index index.html;
}
location /account {
proxy_ssl_server_name on;
...
