Merge pull request #152 from holaplex/espi/hub-ui-web3

[HUB UI] Secrets for Web3 up

Author: kespinola

charts/hub-ui/Chart.yaml

@@ -18,7 +18,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.4.0
+version: 0.5.0
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/hub-ui/templates/secrets.yaml

@@ -10,5 +10,7 @@ type: Opaque
 data:
   NFT_STORAGE_TOKEN: {{ required "must set nft storage token" .entries.nftStorageToken | b64enc }}
   STRIPE_SECRET_KEY: {{ required "must set stripe secret key" .entries.stripeSecretKey | b64enc }}
+  W3_UP_KEY: {{ required "must set w3 up key" .entries.w3UpKey | b64enc }}
+  W3_UP_PROOF: {{ required "must set w3 up proof" .entries.w3UpProof | b64enc }}
 {{- end }}
 {{- end }}

charts/hub-ui/values.yaml

@@ -25,10 +25,12 @@ serviceAccount:
 
 podAnnotations: {}
 
-podSecurityContext: {}
+podSecurityContext:
+  {}
   # fsGroup: 2000
 
-securityContext: {}
+securityContext:
+  {}
   # capabilities:
   #   drop:
   #   - ALL
@@ -40,7 +42,8 @@ service:
   type: ClusterIP
   port: 80
 
-resources: {}
+resources:
+  {}
   # We usually recommend not to specify default resources and to leave this as a conscious
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following
@@ -87,3 +90,5 @@ secrets:
   entries:
     nftStorageToken:
     stripeSecretKey:
+    w3UpKey:
+    w3UpProof: