Course lesson 03 · Getting Started

Deploy the project

One study unit · Read, recall, then practice · Original video 00:05:50

The first deployment turns the working starter into a live Cloudflare Worker application. Wrangler reads the application configuration, builds the project through its deploy script, and uploads both static browser assets and server code. Deploying early makes the hosting process a familiar development step before the product becomes complicated.

Primary source: course video 03 · Supplied English subtitles · 00:05:50.

Understand the idea

What the course does

  1. Create or use a Cloudflare account and find the Workers area of its dashboard.
  2. Inspect the user application’s Wrangler configuration and deployment script.
  3. Run its deploy script from the application directory; complete the CLI’s browser authentication flow when prompted.
  4. Wait for the build and upload to complete, then open the returned workers.dev URL.
  5. Visit the deployed dashboard and inspect its Cloudflare deployment record, asset binding, and observability settings.

Watch for

Recall before revealing

What two kinds of output are uploaded when this application is deployed?

Reveal the explanation

Static browser assets and the server-side Worker bundle; they serve different parts of the application.

Try it

Deploy the starter from your course checkout and trace its deployed name and entrypoint back to the Wrangler file.

Check your result

The returned URL loads the same starter interface and the matching Worker appears in your account.

Practice prompts and answer checks are added teaching material. Answer from memory first, then compare and explain any difference.

Rewatch only what you need

Open this lesson in your original course library and seek to the times below. Videos are not hosted on this site.

Companion primary documentation: Cloudflare Workers runtime APIs. For recorded API names, commands, limits, and prices, check the version you use.

← Previous   Next →