@ -24,13 +24,13 @@ The following guides are based on some shared assumptions:
1. Run this command to build the docs:
1. Run this command to build the docs:
```sh
```sh
$ npm run docs:build
npm run docs:build
```
```
2. Once built, preview it locally by running:
2. Once built, preview it locally by running:
```sh
```sh
$ npm run docs:preview
npm run docs:preview
```
```
The `preview` command will boot up a local static web server that will serve the output directory `.vitepress/dist` at `http://localhost:4173`. You can use this to make sure everything looks good before pushing to production.
The `preview` command will boot up a local static web server that will serve the output directory `.vitepress/dist` at `http://localhost:4173`. You can use this to make sure everything looks good before pushing to production.
@ -294,6 +294,12 @@ You can deploy your VitePress website on [Kinsta](https://kinsta.com/static-site
You can deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
You can deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
### Azion
[Azion](https://www.azion.com/en/) is a web platform that allows you to deploy your VitePress site globally. It provides an efficient way to host your website with low latency and high availability.
You can follow [this guide](https://www.azion.com/en/documentation/products/guides/vitepress-typescript-boilerplate/) to set it up.
### Nginx
### Nginx
Here is a example of an Nginx server block configuration. This setup includes gzip compression for common text-based assets, rules for serving your VitePress site's static files with proper caching headers as well as handling `cleanUrls: true`.
Here is a example of an Nginx server block configuration. This setup includes gzip compression for common text-based assets, rules for serving your VitePress site's static files with proper caching headers as well as handling `cleanUrls: true`.