5.1 KiB
Deploying
The following guides are based on some shared assumptions:
-
You are placing your docs inside the
docs
directory of your project. -
You are using the default build output location (
.vitepress/dist
). -
VitePress is installed as a local dependency in your project, and you have set up the following scripts in your
package.json
:{ "scripts": { "docs:build": "vitepress build docs", "docs:serve": "vitepress serve docs" } }
::: tip
If your site is to be served at a subdirectory (https://example.com/subdir/
), then you have to set '/subdir/'
as the base
in your docs/.vitepress/config.js
.
Example: If you're using Github (or GitLab) Pages and deploying to user.github.io/repo/
, then set your base
to /repo/
.
:::
Build and Test Locally
-
You may run this command to build the docs:
$ yarn docs:build
-
Once you've built the docs, you can test them locally by running:
$ yarn docs:serve
The
serve
command will boot up a local static web server that will serve the files from.vitepress/dist
athttp://localhost:5000
. It's an easy way to check if the production build looks fine in your local environment. -
You can configure the port of the server by passing
--port
as an argument.{ "scripts": { "docs:serve": "vitepress serve docs --port 8080" } }
Now the
docs:serve
method will launch the server athttp://localhost:8080
.
Netlify, Vercel, AWS Amplify, Cloudflare Pages, Render
Set up a new project and change these settings using your dashboard:
- Build Command:
yarn docs:build
- Output Directory:
docs/.vitepress/dist
- Node Version:
14
(or above, by default it usually will be 14 or 16, but on Cloudflare Pages the default is still 12, so you may need to change that)
::: warning Don't enable options like Auto Minify for HTML code. It will remove comments from output which have meaning to Vue. You may see hydration mismatch errors if they get removed. :::
GitHub Pages
Using GitHub Actions
-
Create a file named
deploy.yml
inside.github/workflows
directory of your project with the following content:name: Deploy on: push: branches: - main jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v3 with: node-version: 16 cache: yarn - run: yarn install --frozen-lockfile - name: Build run: yarn docs:build - name: Deploy uses: peaceiris/actions-gh-pages@v3 with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: docs/.vitepress/dist
::: tip Please replace the corresponding branch name. For example, if the branch you want to build is
master
, then you should replacemain
withmaster
in the above file. ::: -
Now commit your code and push it to the
main
branch. -
Wait for actions to complete. Then select
gh-pages
branch as GitHub Pages source in your repository settings. Now your docs will automatically deploy each time you push.
GitLab Pages
Using GitLab CI
-
Set
outDir
indocs/.vitepress/config.js
to../public
. -
Create a file called
.gitlab-ci.yml
in the root of your project with the content below. This will build and deploy your site whenever you make changes to your content:image: node:16 pages: cache: paths: - node_modules/ script: - yarn install - yarn docs:build artifacts: paths: - public only: - main
Azure Static Web Apps
-
Follow the official documentation.
-
Set these values in your configuration file (and remove the ones you don't require, like
api_location
):app_location
:/
output_location
:docs/.vitepress/dist
app_build_command
:yarn docs:build
Firebase
-
Create
firebase.json
and.firebaserc
at the root of your project:firebase.json
:{ "hosting": { "public": "docs/.vitepress/dist", "ignore": [] } }
.firebaserc
:{ "projects": { "default": "<YOUR_FIREBASE_ID>" } }
-
After running
yarn docs:build
, run this command to deploy:firebase deploy
Surge
-
After running
yarn docs:build
, run this command to deploy:npx surge docs/.vitepress/dist
Heroku
-
Follow documentation and guide given in
heroku-buildpack-static
. -
Create a file called
static.json
in the root of your project with the below content:{ "root": "docs/.vitepress/dist" }