|
| 1 | +--- |
| 2 | +title: Deploy static sites to Workers without a configuration file |
| 3 | +description: Wrangler now guides you through deploying static assets with interactive prompts and automatic configuration generation when no wrangler.jsonc file exists. |
| 4 | +products: |
| 5 | + - workers |
| 6 | +date: 2025-09-09 |
| 7 | +--- |
| 8 | + |
| 9 | +Deploying static site to Workers is now easier. When you run `wrangler deploy [directory]` or `wrangler deploy --assets [directory]` without an existing [configuration file](/workers/wrangler/configuration/), [Wrangler CLI](/workers/wrangler/) now guides you through the deployment process with interactive prompts. |
| 10 | + |
| 11 | +## Before and after |
| 12 | + |
| 13 | +**Before:** Required remembering multiple flags and parameters |
| 14 | +```bash |
| 15 | +wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project |
| 16 | +``` |
| 17 | + |
| 18 | +**After:** Simple directory deployment with guided setup |
| 19 | +```bash |
| 20 | +wrangler deploy dist |
| 21 | +# Interactive prompts handle the rest as shown in the example flow above |
| 22 | +``` |
| 23 | + |
| 24 | +## What's new |
| 25 | + |
| 26 | +**Interactive prompts for missing configuration:** |
| 27 | +- Wrangler detects when you're trying to deploy a directory of static assets |
| 28 | +- Prompts you to confirm the deployment type |
| 29 | +- Asks for a project name (with smart defaults) |
| 30 | +- Automatically sets the compatibility date to today |
| 31 | + |
| 32 | +**Automatic configuration generation:** |
| 33 | +- Creates a `wrangler.jsonc` file with your deployment settings |
| 34 | +- Stores your choices for future deployments |
| 35 | +- Eliminates the need to remember complex command-line flags |
| 36 | + |
| 37 | +## Example workflow |
| 38 | + |
| 39 | +```bash |
| 40 | +# Deploy your built static site |
| 41 | +wrangler deploy dist |
| 42 | + |
| 43 | +# Wrangler will prompt: |
| 44 | +✔ It looks like you are trying to deploy a directory of static assets only. Is this correct? … yes |
| 45 | +✔ What do you want to name your project? … my-astro-site |
| 46 | + |
| 47 | +# Automatically generates a wrangler.jsonc file and adds it to your project: |
| 48 | +{ |
| 49 | + "name": "my-astro-site", |
| 50 | + "compatibility_date": "2025-09-09", |
| 51 | + "assets": { |
| 52 | + "directory": "dist" |
| 53 | + } |
| 54 | +} |
| 55 | + |
| 56 | +# Next time you run wrangler deploy, this will use the configuration in your newly generated wrangler.jsonc file |
| 57 | +wrangler deploy |
| 58 | +``` |
| 59 | + |
| 60 | +## Requirements |
| 61 | + |
| 62 | +- You must use Wrangler version 4.24.4 or later in order to use this feature |
| 63 | + |
0 commit comments