mystack

A starting point. With a point of view.

View on GitHub

Configuration

Choose a compatible stack and make the CLI reproducible.

The project wizard

Run the published package through Bunx. Choose a database, runtime, email transport and any subset of payment providers. Arrow keys navigate, Space toggles payment providers, and Enter confirms. Escape or Ctrl-C cancels before creation.

The project wizard
bunx @0x0501/mystack@latest create my-app

Explicit flags

Use --yes to skip prompts. Supply all four categories to make the selection explicit. The CLI uses the same compatibility rules as the website builder. --payments none removes payment integrations; otherwise the default payment provider is Stripe.

Explicit flags
bunx @0x0501/mystack@latest create local-app --yes --database bun-sqlite --deployment bun --email resend --payments none

Database and runtime

PostgreSQL direct connections support Nitro and Bun. Hyperdrive and D1 require Cloudflare Workers. Turso Cloud supports all three runtimes; local libSQL supports Nitro and Bun. Native Bun SQLite requires Bun. Cloudflare Email requires Workers; Resend supports all runtimes.

Dependency installation

Add --no-install to generate files without installing dependencies. If installation fails, the generated application remains in place. Enter its directory and run bun install to retry.

Dependency installation
cd my-app
bun install

The creation record

mystack.json records the choices used to generate the application. It is not a live reconfiguration API. Editing the file does not regenerate source, switch database engines or migrate existing data. Modify the generated source deliberately when your requirements change.