For bands · from a fan

Cloudflare just opened in the other tab. Here’s what it’s asking you.

Keep this tab open beside it. Nothing here costs money and nothing you do in the next ten minutes is permanent — a store you don’t like can be deleted and redone.

Back to the stepsBack to For bandsOpen Cloudflare again

What it asks, in order

1. Sign in to GitHub, then Cloudflare.

   Both free. GitHub holds the code, Cloudflare runs it. If you don’t have them, make them in the band’s name rather than one member’s personal account — it matters later when someone leaves the band.

2. A project name nobody has used.

   Something like yourband-store. It becomes part of your free web address, and you can put your own domain in front of it afterwards.

3. STRIPE_SECRET_KEY.

   From Stripe: Developers → API keys → Secret key → Reveal. It starts with sk_test_. Use the test key first. Not the Publishable key (pk_), which is the one Stripe shows you first and the mistake almost everyone makes.

4. ADMIN_KEY.

   Any long random string you invent. Nobody needs to remember it. It protects the back-in-stock list.

5. Leave the rest blank and press Deploy.

   Two or three minutes. When it finishes you get an address ending .workers.dev. That is your store, live, on the internet.

When it goes wrong

“Cloudflare could not create the Git repository”

That project name is already taken in your GitHub account. Change the name and press Deploy again. Nothing is broken.

It deployed, but the store says checkout isn’t connected

Open your-address/api/setup. It checks the store in plain words and names whatever is wrong — a key pasted short, the publishable key instead of the secret one, a missing address. Fix that one thing and reload it.

I pasted the wrong Stripe key

Cloudflare → your worker → Settings → Variables and Secrets → edit STRIPE_SECRET_KEY → paste the right one. It takes effect immediately; you do not redeploy.

I don’t want to do this part myself

You don’t have to. The agent prompts hand the whole job to a coding assistant, and it will ask you for exactly these same five things.

I want to stop and come back later

Close the Cloudflare tab. Nothing is half-made, nothing is charged. The one-hour checklist is printable if you’d rather do it on paper first.

After it’s live

Three things, in this order, and none of them is urgent. Put a real contact address in store.json, because that’s where a buyer with a problem writes and an unread address is how a small problem becomes a chargeback. Put your own products in. Then, only when you’re ready to take real money, swap the Stripe test key for the live one and buy something yourself with a real card to see it work end to end.

Back to the stepsThe long version

Written by a fan.No affiliate links; nobody here is paid by Cloudflare, GitHub or Stripe.Stuck on something this page doesn’t cover? Tell us and it gets added.