fix: add missing NEXT_PUBLIC_FIXED_STAKING_TERM (#622)

babylonlabs-io · Jan 10, 2025 · 72f2313 · 72f2313
1 parent 25a35a9
commit 72f2313
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 1 deletion.
diff --git a/.env.example b/.env.example
@@ -2,4 +2,5 @@ NEXT_PUBLIC_MEMPOOL_API=https://mempool.space
 NEXT_PUBLIC_API_URL=https://staking-api.phase-2-devnet.babylonlabs.io
 NEXT_PUBLIC_NETWORK=signet
 NEXT_PUBLIC_DISPLAY_TESTING_MESSAGES=true
-NEXT_PUBLIC_SENTRY_DSN=http://[email protected]:9000/1
+NEXT_PUBLIC_SENTRY_DSN=http://[email protected]:9000/1
+NEXT_PUBLIC_FIXED_STAKING_TERM=true
diff --git a/.github/workflows/publish.yaml b/.github/workflows/publish.yaml
@@ -50,6 +50,7 @@ jobs:
             NEXT_PUBLIC_NETWORK=${{ vars.NEXT_PUBLIC_NETWORK }}
             NEXT_PUBLIC_DISPLAY_TESTING_MESSAGES=${{ vars.NEXT_PUBLIC_DISPLAY_TESTING_MESSAGES }}
             NEXT_PUBLIC_SENTRY_DSN=${{ vars.NEXT_PUBLIC_SENTRY_DSN }}
+            NEXT_PUBLIC_FIXED_STAKING_TERM=${{ vars.NEXT_PUBLIC_FIXED_STAKING_TERM }}
             NEXT_PUBLIC_COMMIT_HASH=${{ github.sha }}
       - name: Upload Docker image to workspace
         uses: actions/upload-artifact@v4

diff --git a/README.md b/README.md
@@ -23,6 +23,7 @@ where,
 - `NEXT_PUBLIC_NETWORK` specifies the BTC network environment
 - `NEXT_PUBLIC_DISPLAY_TESTING_MESSAGES` boolean value to indicate whether display 
 testing network related message. Default to true
+- `NEXT_PUBLIC_FIXED_STAKING_TERM` boolean value to indicate whether the staking term is fixed. Default to false
 
 Then, to start a development server:
 

diff --git a/docker/Dockerfile b/docker/Dockerfile
@@ -32,6 +32,9 @@ ENV NEXT_PUBLIC_SENTRY_DSN=${NEXT_PUBLIC_SENTRY_DSN}
 ARG NEXT_PUBLIC_COMMIT_HASH
 ENV NEXT_PUBLIC_COMMIT_HASH=$NEXT_PUBLIC_COMMIT_HASH
 
+ARG NEXT_PUBLIC_FIXED_STAKING_TERM
+ENV NEXT_PUBLIC_FIXED_STAKING_TERM=${NEXT_PUBLIC_FIXED_STAKING_TERM}
+
 RUN npm run build
 
 # Step 2. Production image, copy all the files and run next