Skip to content

est: fix deploy script #44

est: fix deploy script

est: fix deploy script #44

Workflow file for this run

name: Pages
on:
push:
branches:
- master # default branch
pull_request:
jobs:
pages:
runs-on: ubuntu-latest
environment:
name: Production
url: ${{ steps.deploy_to_pages.outputs.github_pages_url }}
permissions:
contents: write
pages: write
id-token: write
steps:
- uses: actions/checkout@v2
- name: Use Node.js 18
uses: actions/setup-node@v2
with:
node-version: "18"
- name: Cache NPM dependencies
uses: actions/cache@v2
with:
path: node_modules
key: ${{ runner.OS }}-npm-cache
restore-keys: |
${{ runner.OS }}-npm-cache
- run: npm ci
- name: Install Dependencies
run: npm install
- name: MakeCategory
run: |
cd ./public
./makeCategory
cd ../
- name: Build
run: npm run build
- name: Deploy
uses: skywarth/[email protected]
with:
# Public base path string for vite, this affects the routing, history and asset links. Make sure to provide appropriately since Github Pages stores your app in a directory under a subdomain.
# Which folder do you want your Github Page to use as root directory. Usually it is your build output directory such as ./dist
build_path: ./website
# Node env that will be used for the installation of dependencies. It is imperative you use an environment that has 'vite' as dependency. Commonly, that is 'dev'.
# Node env that will be used for build phase.
# Your preference of package manager: 'npm' and 'yarn' are possible values.
package_manager: npm
# Desired name for the Deployment environment. It is also the exposed artifact name which contains the build output (dist).
# Controls the debug mode, boolean, true is for on. When turned on, it'll output certain information on certain steps. Mainly used for development, but use it as you please to inspect your env and variables