Implementation:Dagster io Dagster Vercel Redirect Configuration
| Knowledge Sources | |
|---|---|
| Domains | Documentation, Deployment, URL_Management |
| Last Updated | 2026-02-10 12:30 GMT |
Overview
Concrete tool for configuring the Vercel deployment pipeline and URL redirect rules for the Dagster documentation site.
Description
The vercel.json file (4,439 lines) is the deployment configuration for docs.dagster.io hosted on Vercel. It serves two primary purposes: (1) defining the build command chain that sequentially runs build-api-docs, build-kinds-tags, and the main Docusaurus build, and (2) maintaining an extensive list of URL redirects (~4,400 lines) that map legacy documentation paths to their current locations. These redirects ensure backward compatibility of bookmarks, search engine indexes, and external links when the documentation structure is reorganized.
Usage
Modify this file when documentation URLs change due to restructuring, when pages are moved or renamed, or when new build steps need to be added to the deployment pipeline. Every URL path change in the docs site should have a corresponding redirect entry here to avoid broken links.
Code Reference
Source Location
- Repository: Dagster_io_Dagster
- File: docs/vercel.json
- Lines: 1-4439
Signature
{
"buildCommand": "echo 'Starting build...' && yarn build-api-docs && yarn build-kinds-tags && yarn build",
"redirects": [
{
"source": "/dagster-cloud/insights",
"destination": "/guides/observe/insights"
},
{
"source": "/dagster-cloud/:path*",
"destination": "/deployment/dagster-plus/:path*"
}
// ... ~4400 lines of redirect rules
]
}
Import
# This file is consumed automatically by the Vercel platform during deployment.
# No manual import is needed. Place at the root of the docs/ directory.
I/O Contract
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
| buildCommand | string | Yes | Shell command chain executed during Vercel builds |
| redirects | Array of redirect objects | Yes | Each object has source (old path pattern), destination (new path), and optional permanent flag |
| source (redirect) | string | Yes | URL pattern to match (supports * and :path* wildcards) |
| destination (redirect) | string | Yes | Target URL to redirect to |
| permanent (redirect) | boolean | No | If true, uses 308 permanent redirect; defaults to 308 |
Outputs
| Name | Type | Description |
|---|---|---|
| Build pipeline | Vercel build | Executes API docs generation, kinds/tags build, then main Docusaurus build |
| HTTP redirects | 308/307 responses | Vercel edge network serves redirects for matched source patterns |
Usage Examples
Adding a Simple Redirect
{
"redirects": [
{
"source": "/old-page",
"destination": "/new-page"
}
]
}
Adding a Wildcard Redirect for a Renamed Section
{
"redirects": [
{
"source": "/concepts/assets/:path*",
"destination": "/guides/build/assets/:path*"
}
]
}
Adding a Temporary (Non-Permanent) Redirect
{
"redirects": [
{
"source": "/beta-feature",
"destination": "/guides/labs/beta-feature",
"permanent": false
}
]
}