TanStarter CLI

English | 简体中文

Create a production-ready TanStarter app from the template and deploy it to Cloudflare Workers in about 10 minutes.

export CLOUDFLARE_ACCOUNT_ID="..."
export CLOUDFLARE_API_TOKEN="..."

# Optional: enable Waffo payments during setup
export WAFFO_MERCHANT_ID="MER_..."
export WAFFO_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----..."

npx tanstarter-cli@latest create

TanStarter CLI will ask for the project name, resource names, and payment method before creating anything. When you pick Waffo, it also creates a Waffo store, the three template products, and the webhook automatically.

To keep the payment prompt but accept every other default (domain, D1/R2/KV names, GitHub repository, and final confirmation), pass --yes:

npx tanstarter-cli@latest create my-app --yes

Install the TanStarter creation skill for Codex, Claude Code, or another supported agent:

npx skills add MkFastHQ/tanstarter-cli --skill tanstarter-create

Run without installing:

npx tanstarter-cli@latest create

Or install globally:

npm install -g tanstarter-cli

Then run:

tanstarter create

tanstarter create [options]
tanstarter delete <project-name> [options]
tanstarter create <project-name> --resume

Options:

• --domain <domain>: configure a Cloudflare custom domain route.
• --payment <none|waffo>: payment method for the generated project. With waffo, the CLI uses the template's built-in monthly, yearly, and lifetime products, then creates the Waffo store, products, and webhook during setup.
• -y, --yes: accept default domain, resource names, GitHub repository, and final confirmation. It still asks for payment unless --payment is set.
• --repo <owner/name>: create this GitHub repository. If omitted, TanStarter CLI defaults to the current GitHub CLI login and project name, for example open-fox/my-app.
• --resume: continue a failed setup from .tanstarter/state.json.
• -h, --help: show help.
• -v, --version: show version.

Example:

tanstarter create --domain app.example.com --repo mkfasthq/my-app

If a run fails after the project directory is created, fix the issue and run:

tanstarter create my-app --resume

To delete the Cloudflare and GitHub resources created by the CLI, run:

tanstarter delete my-app

• Node.js 20 or later.
• A Cloudflare account with CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_TOKEN available in your shell environment.
• A GitHub account authenticated with GitHub CLI.
• (Waffo only) Create a Test API Key in the Waffo dashboard (API & Development → API Keys). Use the MER_... merchant ID as WAFFO_MERCHANT_ID and the private key value provided by Waffo as WAFFO_PRIVATE_KEY; the CLI passes that value through unchanged. The CLI always uses Waffo test mode and falls back to the deployed workers.dev URL when no custom domain is supplied.

The CLI checks for node, pnpm, git, gh, GitHub CLI auth, and Cloudflare credentials. If pnpm, git, or gh is missing, the CLI attempts to install it with the available system package manager before continuing.

When running without a TTY, pass --payment waffo. No store/product fields or extra Waffo environment variables are required; the CLI uses the template's built-in pricing. --domain is optional:

npx tanstarter-cli@latest create my-app --payment waffo

The CLI creates a project-named store and three products matching the template: Pro Monthly at $9.90, Pro Yearly at $99.00, and Lifetime at $199.00. Their IDs are written to VITE_WAFFO_PRODUCT_PRO_MONTHLY, VITE_WAFFO_PRODUCT_PRO_YEARLY, and VITE_WAFFO_PRODUCT_LIFETIME, then the site is deployed, Worker secrets are synchronized, the public URL is verified, and https://<domain>/api/webhooks/waffo (or the deployed workers.dev equivalent) is registered. The deployed Worker keeps WAFFO_DEBUG=true, so the online site uses Waffo test payments.

The CLI always provisions Waffo in test mode. Live product publishing is outside this setup flow.

Waffo may still require merchant verification, business details, or payout setup in its dashboard.

The setup flow:

1. Clones the TanStarter template and preserves its Git history.
2. Installs dependencies with pnpm install.
3. Verifies Cloudflare authentication.
4. (Waffo only) Creates the Waffo store and three template products.
5. Creates Cloudflare D1, R2, and KV resources.
6. Updates wrangler.jsonc and writes .env/.env.production.
7. Runs database migrations.
8. Builds and deploys locally.
9. Syncs Worker secrets.
10. Verifies the public deployment URL.
11. (Waffo only) Registers the webhook after the deployed route is reachable.
12. Creates a GitHub repository.
13. Syncs GitHub Actions secrets.
14. Commits and pushes to main.

The generated repository uses origin for your new GitHub repository and upstream for https://github.com/MkFastHQ/mkfast-template.git. Because the template history is preserved, future template updates can use a normal Git merge instead of reconstructing a common ancestor.

Environment variables from the template .env.example are copied from your shell into the generated .env and .env.production files when present. Generated Cloudflare, D1, KV, base URL, and auth secret values take precedence.

• Website: tanstarter.dev
• CLI documentation: docs.tanstarter.dev/docs/cli
• CLI video tutorial: youtu.be/HVwilCX6YSA

If you have questions, contact support@tanstarter.dev or join the Discord community.

MIT