@willemarcel found a feature in the nextConfig to put a trailingSlash: true and that would export each route into a folder. This seem to work now!
~After wrangling a bunch with GCP deploys, I've made this PR to just deploy to surge.sh~
~@oliverroick there's no way to deploy to GCP storage and use frontend routing. Then our options are to use a GCP app engine or package as part of our k8s cluster — both are a bit much right now so let's just go with this if you don't have strong disagreement.~
~This will deploy staging to ecoecho-staging.surge.sh~
This PR now deploys to a GCP storage and serves the frontend on https://ecoecho.ds.io via a GCP loadbalancer + CDN managed by https://github.com/developmentseed/bioacoustics-deploy/pull/8
@willemarcel found a feature in the nextConfig to put a
trailingSlash: trueand that would export each route into a folder. This seem to work now!~After wrangling a bunch with GCP deploys, I've made this PR to just deploy to surge.sh~
~@oliverroick there's no way to deploy to GCP storage and use frontend routing. Then our options are to use a GCP app engine or package as part of our k8s cluster — both are a bit much right now so let's just go with this if you don't have strong disagreement.~
~This will deploy staging to ecoecho-staging.surge.sh~
cc @sunu