Pages Deployment

Deploying static sites with wrangler pages deploy

Creating a Pages Project

Before your first deploy, create the project:

npx wrangler@4 pages project create zudo-cloudflare

Or let the first pages deploy create it automatically.

Deploy Command

The core deploy command:

npx wrangler@4 pages deploy <directory> \
  --project-name=<project-name> \
  --branch=<branch> \
  --commit-hash="${GITHUB_SHA}" \
  --commit-message="Production deploy: ${GITHUB_SHA}"

Parameters

Environment Variables

The deploy command needs these environment variables:

CLOUDFLARE_API_TOKEN=<your-token>
CLOUDFLARE_ACCOUNT_ID=<your-account-id>

Production vs Preview

• Production: Deploy with --branch=main. This updates the primary URL.

• Preview: Deploy with any other branch name (e.g., --branch=pr-42). This creates a preview URL.

Deploy Directory Structure

The deploy directory must contain the final files as they should be served. If your site uses a base path (e.g., /pj/my-site/), you need to nest files accordingly:

mkdir -p deploy/pj/my-site
cp -r dist/* deploy/pj/my-site/
echo '/ /pj/my-site/ 302' > deploy/_redirects
npx wrangler@4 pages deploy deploy --project-name=my-site --branch=main

See Base Path Pattern for details.