Skip to content

Commit

Permalink
fix: environment vars and build directory for deploy
Browse files Browse the repository at this point in the history
  • Loading branch information
bucko13 committed Feb 15, 2024
1 parent 888b3bb commit 3efceb1
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 9 deletions.
13 changes: 6 additions & 7 deletions .github/workflows/deploy.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,8 @@ jobs:
deploy:
name: Deploy
runs-on: ubuntu-latest
# To use Turborepo Remote Caching
env:
TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
TURBO_TEAM: ${{ vars.TURBO_TEAM }}
GITHUB_PAGES: true

steps:
- name: Checkout Repo
Expand All @@ -35,12 +33,13 @@ jobs:
# sub directory of the monorepo, even if we reference it correctly
# so we have to copy it to the root of the repo.
- name: Build
run: |
npx turbo run build
cp -R apps/coordinator ./build
# forcing a build to avoid the cache. Probably unnecessary
# but useful in case any environment variables change that might
# impact the build
run: npx turbo run build --force

- name: Deploy to GitHub Pages
uses: JamesIves/github-pages-deploy-action@v4
with:
branch: gh-pages
folder: build
folder: apps/coordinator/build
4 changes: 2 additions & 2 deletions apps/coordinator/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@caravan/coordinator",
"version": "0.0.3",
"version": "0.0.2",
"description": "Unchained Capital's Bitcoin Multisig Coordinator Application",
"main": "index.jsx",
"private": true,
Expand Down Expand Up @@ -69,7 +69,7 @@
"build:ci": "npm run ci && tsc && __GIT_SHA__=`git rev-parse --short HEAD` vite build",
"check": "npm run lint && npm run test:ci",
"ci": "npm run lint && npm run test:ci",
"deploy": "gh-pages -d build",
"deploy": "GH_PAGES=true gh-pages -d build",
"gh-pages": "CI=true npm run build && gh-pages -d build",
"lint": "eslint --ext .js,.jsx,.ts,.tsx src/",
"predeploy": "npm run build",
Expand Down

0 comments on commit 3efceb1

Please sign in to comment.