Deploying to Cloudflare Pages in Astro - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize a new Astro project for Cloudflare Pages deployment.

Astro

npm init astro@latest -- --template [1]

Drag options to blanks, or click blank then click option'

Acloudflare

Bdocs

Cblog

Dminimal

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a template that is too complex for Cloudflare Pages.

Using a template not supported by Astro CLI.

The minimal template is a good starting point for deploying Astro projects to Cloudflare Pages.

2fill in blank

medium

Complete the command to install the Cloudflare adapter for Astro.

Astro

npm install @astrojs/[1]

Drag options to blanks, or click blank then click option'

Acloudflare

Bvercel

Cnetlify

Dgithub

Attempts:

3 left

💡 Hint

Common Mistakes

Installing the wrong adapter for the deployment platform.

Forgetting to install the adapter before building.

The @astrojs/cloudflare adapter is required to deploy Astro projects to Cloudflare Pages.

3fill in blank

hard

Fix the error in the Astro config to use the Cloudflare adapter.

Astro

import cloudflare from '@astrojs/cloudflare/worker';

export default {
  adapter: [1](),
};

Drag options to blanks, or click blank then click option'

Avercel

Bcloudflare

Cnetlify

Dgithub

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong adapter name.

Not calling the adapter as a function.

The adapter must be called as a function from the imported cloudflare object.

4fill in blank

hard

Fill both blanks to complete the build and deploy commands for Cloudflare Pages.

Astro

npm run [1]
wrangler [2]

Drag options to blanks, or click blank then click option'

Abuild

Bpublish

Cdeploy

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Running deploy before building.

Using wrong wrangler commands.

First, build the project with npm run build. Then deploy using wrangler publish.

5fill in blank

hard

Fill all three blanks to configure the Astro project for Cloudflare Pages deployment.

Astro

import [1] from '@astrojs/cloudflare/worker';

export default {
  adapter: [2](),
  build: {
    [3]: 'service-worker'
  }
};

Drag options to blanks, or click blank then click option'

Acloudflare

Cformat

Dtarget

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong property names in build config.

Mismatching import and adapter names.

Import the cloudflare adapter, use it in adapter, and set target to service-worker for Cloudflare Pages.

Practice

1. What is the first step to deploy an Astro site to Cloudflare Pages?

easy

A. Push your Astro project code to a GitHub repository

B. Write a custom server script for Cloudflare

C. Install Cloudflare Pages CLI locally

D. Create a Docker container for the site

Solution

1. Step 1: Prepare your Astro project

   You need to have your Astro site code ready and pushed to a GitHub repository because Cloudflare Pages connects to GitHub to get your code.

2. Step 2: Connect GitHub repo to Cloudflare Pages

   Cloudflare Pages uses your GitHub repository to build and deploy your site automatically.

3. Final Answer:

   Push your Astro project code to a GitHub repository -> Option A

4. Quick Check:

   First step is pushing code to GitHub [OK]

Hint: Remember: Cloudflare Pages pulls from GitHub first [OK]

Common Mistakes:

• Trying to deploy without a GitHub repo
• Assuming local CLI is mandatory
• Thinking Docker is required

2. Which build command is typically used in Cloudflare Pages settings for an Astro project?

easy

A. astro dev

B. npm run start

C. npm run build

D. npm install

Solution

1. Step 1: Understand Astro build process

   Astro projects use npm run build to create the static files for deployment.

2. Step 2: Set build command in Cloudflare Pages

   Cloudflare Pages needs the build command to generate the site files; npm run build is the correct command.

3. Final Answer:

   npm run build -> Option C

4. Quick Check:

   Build command = npm run build [OK]

Hint: Build command for Astro is always npm run build [OK]

Common Mistakes:

• Using npm run start which runs a dev server
• Using astro dev which is for local development
• Confusing install with build

3. Given this Cloudflare Pages config snippet:

build:
  command: "npm run build"
  directory: "dist"

What will Cloudflare Pages do after you push your Astro site code?

medium

A. Run npm install and deploy files from node_modules

B. Run npm run build and deploy files from the dist folder

C. Ignore build and deploy all files in the repo

D. Run npm start and deploy files from the root folder

Solution

1. Step 1: Read the build command

   The config says to run npm run build, which builds the Astro site into static files.

2. Step 2: Check the output directory

   The directory dist is where Astro puts the built site files, so Cloudflare Pages deploys from there.

3. Final Answer:

   Run npm run build and deploy files from the dist folder -> Option B

4. Quick Check:

   Build command + output folder = deploy [OK]

Hint: Build command runs, output folder is deployed [OK]

Common Mistakes:

• Confusing npm start with build
• Deploying from wrong folder
• Thinking node_modules is deployed

4. You connected your GitHub repo to Cloudflare Pages but the deployment fails with "Build command not found" error. What is the likely cause?

medium

A. You pushed code to the wrong GitHub branch

B. You used the wrong Cloudflare account

C. You did not enable GitHub Actions

D. You forgot to add a build script in package.json

Solution

1. Step 1: Understand the error message

   "Build command not found" means Cloudflare tried to run the build command but it does not exist in your project.

2. Step 2: Check package.json scripts

   The build command must be defined in the scripts section of package.json, usually as "build": "astro build" or similar.

3. Final Answer:

   You forgot to add a build script in package.json -> Option D

4. Quick Check:

   Missing build script causes build command error [OK]

Hint: Check package.json scripts for build command [OK]

Common Mistakes:

• Assuming branch or account causes build command error
• Thinking GitHub Actions must be enabled manually
• Ignoring package.json scripts

5. You want to deploy an Astro site with environment variables on Cloudflare Pages. Which step is necessary to ensure your variables are available during build?

hard

A. Add environment variables in Cloudflare Pages dashboard under Settings > Environment Variables

B. Include variables in a .env file and push it to GitHub

C. Hardcode variables directly in your Astro source code

D. Set variables only in your local machine before pushing

Solution

1. Step 1: Understand environment variable usage in Cloudflare Pages

   Cloudflare Pages requires environment variables to be set in its dashboard to inject them during build securely.

2. Step 2: Avoid pushing .env files with secrets

   For security, do not push .env files with secrets to GitHub; instead, configure variables in Cloudflare Pages settings.

3. Final Answer:

   Add environment variables in Cloudflare Pages dashboard under Settings > Environment Variables -> Option A

4. Quick Check:

   Set env vars in Cloudflare dashboard for build [OK]

Hint: Set env vars in Cloudflare dashboard, not in repo [OK]

Common Mistakes:

• Pushing .env files with secrets publicly
• Hardcoding sensitive info in code
• Assuming local env vars affect cloud build