Say what the deploy button leaves you, and list wrangler as a need

Both guides assumed a local clone without saying so. The Cloudflare
one now opens with a callout naming the exact steps a button user
still has to do, and both note that wrangler comes from npm install
rather than a global install.

Fixes two wrong claims while there: the button was described as doing
"steps 1 through 3 and 5", but it doesn't load the schema (half of
step 2) and doesn't leave you a clone (step 1), which you need for
registering commands. Button users also need to clone their own fork,
not this repo, so the database_id matches what was provisioned.

register-commands now shows the credentials inline, since it reads
them from the shell and Cloudflare secrets can't be read back.

nccommitted 2 months agoparent 8fe0b20052d3f0d14cb718ccd831049ce1688dc833f999fBrowse files