CLI Reference ​

The teeny CLI (alias: teenybase) handles project creation, migrations, deployment, and observability. Every command you need to go from zero to production is here.

Global Options ​

These apply to most commands (generate, deploy, secrets, backup, build, exec). The --local and --remote flags only apply to commands that accept a target. dev always runs locally.

Project Setup ​

create <name> ​

Create a new teenybase project.

teeny create my-app
teeny create my-app --template blank --yes

Creates a directory, scaffolds the project, and runs npm install.

init ​

Initialize teenybase in the current directory. Only creates files that don't already exist — never overwrites.

teeny init
teeny init --template blank

Generated files: package.json, wrangler.jsonc, tsconfig.json, teenybase.ts, src/index.ts, worker-configuration.d.ts, .dev.vars, .gitignore, migrations/

Templates:

• with-auth — Users table with auth (sign-up, login, JWT) and row-level security. Includes common fields (id, created, updated, username, email, password).
• blank — Empty tables. Good for starting from scratch or adding teenybase to an existing project.

Development Workflow ​

deploy ​

Apply migrations and deploy. This is the main command for both local development and production.

teeny deploy --local              # apply migrations locally
teeny deploy --local --yes        # skip confirmation
teeny deploy --remote             # deploy + migrate to production
teeny deploy --remote --no-migrate  # deploy worker only, skip migrations

First-time remote deploy automatically:

1. Deploys a minimal config to capture the worker URL
2. Uploads secrets
3. Applies migrations
4. Deploys full config

generate ​

Generate migration SQL files from config changes without deploying.

teeny generate --local
teeny generate --remote

You usually don't need this separately — deploy runs generate automatically.

dev ​

Start the local dev server.

teeny dev

Prerequisite: Run teeny deploy --local first to set up the local database.

Environment variables:

• TEENY_DEV_PORT — override dev server port (default: 8787)
• TEENY_INSPECTOR_PORT — override inspector port (default: 9229, useful for multiple dev servers)

dev always runs locally. Passing --remote will error.

build ​

Build the worker for production (dry-run deploy with minification).

teeny build --local
teeny build --remote --outDir ./output

exec <route> ​

Execute an API route with the admin service token.

teeny exec users/select --local
teeny exec users/insert --local -m POST -d '{"values":{"name":"test"}}'
teeny exec users/select --local --explain

The route is prefixed with /api/v1/table/ (or /api/v1/explain/table/ with --explain).

backup ​

Back up the database.

teeny backup --local
teeny backup --remote

Creates a timestamped directory at db_backups/{local|remote}/{db-binding}/{timestamp}/ containing the schema, data, config, and migration history.

secrets ​

Manage worker secrets.

teeny secrets --remote              # list keys from .prod.vars
teeny secrets --remote --upload     # upload secrets from .prod.vars

Local mode doesn't need secret uploads — .dev.vars is read automatically by the dev server.

Teenybase Cloud ​

Deploy without your own Cloudflare account. Run register or login, then use deploy --remote as usual.

register ​

teeny register
teeny register --email user@example.com --password mypass

login ​

teeny login
teeny login --email user@example.com --password mypass

logout ​

teeny logout

whoami ​

Show the currently logged-in user.

teeny whoami

list ​

List all your deployed workers.

teeny list

status [name] ​

Show status of a deployed worker (URL, databases, last deploy time).

teeny status
teeny status my-app

If name is omitted, reads from wrangler.jsonc in the current directory.

delete [name] ​

Delete a deployed worker and its databases.

teeny delete my-app
teeny delete my-app --yes

Observability ​

logs [name] ​

Stream live logs from a deployed worker.

teeny logs                            # stream logs for current project
teeny logs my-app                     # stream logs for a specific worker
teeny logs --json                     # output raw JSON (newline-delimited)
teeny logs --since 1m --interval 5s   # look back 1 min, poll every 5s
teeny logs --limit 50                 # stop after 50 events (for CI)

Self-hosted: Requires CLOUDFLARE_API_TOKEN environment variable with Workers:Read permission. Create one at dash.cloudflare.com/profile/api-tokens.

Teenybase Cloud: Authenticates automatically using your login credentials.

Cloudflare has a ~1-2 minute ingestion delay. Logs from recent requests may take a moment to appear.

Common Workflows ​

New project — local development:

teeny create my-app
cd my-app
teeny deploy --local --yes
teeny dev

Schema change:

# Edit teenybase.ts, then:
teeny deploy --local
# Test locally, then:
teeny deploy --remote

First production deploy (Teenybase Cloud):

teeny register
# Verify your email
teeny deploy --remote

First production deploy (own Cloudflare account):

# Ensure wrangler is logged in: npx wrangler login
teeny deploy --remote

Reset local database:

rm -rf .local-persist migrations
teeny deploy --local --yes

Environment Variables ​

Key Files ​