Skip to main content

Deployment

Subdomain (docs.example.com)​

This project is configured as a standalone site with baseUrl: '/'. Point your docs subdomain (for example docs.yourcompany.com) at the contents of the Docusaurus build/ output.

  1. Set the public site URL:

    • Edit docusaurus.config.ts and set docsSiteUrl / url to your real docs origin (for example https://docs.pa-agent.dev), or
    • Set the environment variable DOCS_URL when running npm run build so CI can inject production URLs without editing files.

  2. Build:

    cd docs && npm run build

  3. Upload docs/build/ to your host (S3 + CloudFront, Netlify, Vercel static, Nginx root, and so on).

  4. DNS: create a CNAME (or A/ALIAS) for docs to that host.

The landing page is served at /, Docusaurus docs at /docs/..., and the Open Source marketing page at /opensource.

Same host as another app​

If you must mount under a path (for example https://www.example.com/docs-site/), set baseUrl in docusaurus.config.ts to that path and re-test internal links.