Skip to main content
Creates and starts one or more clones. Allocates an id and ports, ensures shared infra is up, creates and migrates the database, builds and starts the containers, waits for health, and records the clone. See what spin does, end to end.

​
Arguments

The shipping templates are slack, stripe, linear, github, notion, and hubspot. Run hone env ls --templates to see them and the modes each supports.

​
Options

​
Examples

Spin one clone:
Templates that expose an apps/provision surface (today, slack) auto-provision a default app on spin and print a bot + user token for programmatic access. Reprint them later with hone env tokens <id>. Templates without that surface simply omit the token lines. Spin with the full UI and a fixture, in one step:
Spin several clones — even different templates — into one environment:
Both clones become members of environment workspace-1; manage them as a unit with the environment commands. Expose to other machines on your network (use with care):

​
The summary card

Each clone prints two lines:
The endpoint is the API URL if there is one, else the web URL, else (no endpoint). <environment> is the name passed with -g, or - if none. When you pass --seed, a seeded: <fixture> line is printed below. For templates that auto-provision an app, two more lines — bot token and user token — carry the credentials for programmatic access (shown once here; reprint with hone env tokens).

​
Partial failure

Templates are spun independently. If one fails, the others still come up and the failure is printed to stderr; the command exits 1:
A clone that fails mid-create is rolled back automatically — containers and volumes removed, database dropped — so you never get a half-built clone.

​
Errors you might see

See the full error reference.