wrangler
is a CLI tool designed for folks who are interested in using Cloudflare Workers.
You have many options to install wrangler!
npm i @cloudflare/wrangler -g
cargo install wrangler
If you don't have cargo
or npm
installed, you will need to follow these additional instructions.
For information regarding updating Wrangler, click here.
Once you have installed Wrangler, spinning up and deploying your first Worker is easy!
$ wrangler generate my-worker
$ cd my-worker
# update your wrangler.toml with your Cloudflare Account ID
$ wrangler config
$ wrangler publish
Scaffold a project, including boilerplate code for a Rust library and a Cloudflare Worker.
wrangler generate <name> <template> --type=["webpack", "javascript", "rust"]
All of the arguments and flags to this command are optional:
name
: defaults toworker
template
: defaults to thehttps://github.com/cloudflare/worker-template
type
: defaults to "webpack"
Creates a skeleton wrangler.toml
in an existing directory. This can be used as an alternative to generate
if you prefer to clone a repository yourself.
wrangler init <name> --type=["webpack", "javascript", "rust"]
All of the arguments and flags to this command are optional:
name
: defaults to the name of your working directorytype
: defaults to "webpack".
Build your project. This command looks at your wrangler.toml
file and runs the build steps associated
with the "type"
declared there.
Additionally, you can configure different environments.
Configure your global Cloudflare user. This is an interactive command that will prompt you for your API token:
wrangler config
Enter API token:
superlongapitoken
You can also provide your email and global API key (this is not recommended for security reasons):
wrangler config --api-key
Enter email:
testuser@example.com
Enter global API key:
superlongapikey
You can also use environment variables to configure these values.
Publish your Worker to Cloudflare. Several keys in your wrangler.toml
determine whether you are publishing to a workers.dev subdomain or your own registered domain, proxied through Cloudflare.
Additionally, you can configure different environments.
You can also use environment variables to handle authentication when you publish a Worker.
```bash
# e.g.
CF_API_TOKEN=superlongtoken wrangler publish
# where
# $CF_API_TOKEN -> your Cloudflare API token
CF_API_KEY=superlongapikey CF_EMAIL=testuser@example.com wrangler publish
# where
# $CF_API_KEY -> your Cloudflare API key
# $CF_EMAIL -> your Cloudflare account email
```
Interact with your Workers KV store. This is actually a whole suite of subcommands. Read more about in Wrangler KV Documentation.
All information regarding wrangler or Cloudflare Workers is located in the Cloudflare Workers Developer Docs. This includes:
- Using wrangler commands
- Wrangler configuration
- General documentation surrounding Workers development
- All wrangler features such as Workers Sites and KV
To learn about deploying static assets using wrangler
, see the Workers Sites Quickstart.