Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add website staging instructions #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add website staging instructions #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions developer-process/publish-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,13 +80,14 @@
git push
```

### Build the website
### Build and test the website

4. Under the release branch:
```bash
cd website
yarn
yarn build
yarn build # build website
yarn serve # test website locally
```

### Pre-release checks
Expand All @@ -113,3 +114,11 @@ In the website directory, run:
```bash
yarn deploy
```

## Useful Tricks

### Website staging

For [`Gastby`](https://www.gatsbyjs.org/) generated websites, the `index.html` refers to the absolute paths of the generated files under `PATH_PREFIX` (specified in `website/gatsby-config.js`).
So the deployed path needs to match `PATH_PREFIX`. i.e. if you'd like to deploy `loaders.gl` to `<personal>.github.io/loaders.gl` then `PATH_CONFIG` should be set to `/loaders.gl`.
**Note: this is for staging and testing purpose, you should not be commit to production**