feat(filecoin): fix HOSTED_ZONE usage in Filecoin stack

storacha · Sep 6, 2024 · 6b2fb9f · 6b2fb9f
1 parent 3a27b29
commit 6b2fb9f
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -112,9 +112,9 @@ Please notice that appropriate environment variables must be set for the develop
 
 Ensure the following variables are set in the env when deploying
 
-#### `HOSTED_ZONE`
+#### `HOSTED_ZONES`
 
-The root domain to deploy the w3up API to. e.g `up.web3.storage`. The value should match a hosted zone configured in route53 that your aws account has access to.
+The root domain(s) to deploy the w3up API to. e.g `up.web3.storage`. The value should match a hosted zone configured in route53 that your aws account has access to. Multiple zones can be specified, in which case they are seperated by a comma, and this will cause deployment to each specified zone.
 
 #### `ROUNDABOUT_HOSTED_ZONE`
 

diff --git a/stacks/filecoin-stack.js b/stacks/filecoin-stack.js
@@ -31,7 +31,7 @@ export function FilecoinStack({ stack, app }) {
     STOREFRONT_PROOF,
     START_FILECOIN_METRICS_EPOCH_MS
   } = getEnv()
-  const storefrontCustomDomain = getCustomDomain(stack.stage, process.env.HOSTED_ZONE)
+  const storefrontCustomDomain = getCustomDomain(stack.stage, process.env.HOSTED_ZONES?.split(",")[0])
 
   // Setup app monitoring with Sentry
   setupSentry(app, stack)