caravel init

Start a lane: write DIR/lane.toml from a template's example, and create the Stellar CLI identities it names (<name>-<role>)

Start a lane: write DIR/lane.toml from a template's example, and create the Stellar CLI identities it names (`<name>-<role>`)

Usage: caravel init [OPTIONS] [TEMPLATE] [DIR]

Arguments:
  [TEMPLATE]  The template (one of `caravel init --list`); the only one installed, if there is one
  [DIR]       Where to write lane.toml (default: here); its name is the lane's unless --name

Options:
  -f, --file <LANE_FILE>   The lane file, or a directory with a lane.toml (also CARAVEL_FILE)
      --name <NAME>        The lane's name ([lane] name; it fixes the lane's id)
  -e, --env <NAME>         The deployment, [env.<name>] (also CARAVEL_ENV)
      --port <PORT>        The sequencer's port (default: the first free one from 18080; validators take the next ones)
      --json               Print JSON on stdout, for scripts; progress and notes go to stderr
      --prefix <PREFIX>    The identities' prefix (default: the lane's name)
      --force              Replace an existing lane.toml
      --release-dir <DIR>  A release to install (also CARAVEL_RELEASE_DIR); default: the one installed with caravel, else this checkout's builds
      --runtime <RUNTIME>  How the local deployment runs its nodes: `docker` (containers from the release's images) or `process`. Default: docker when the installed release ships images, else process [possible values: docker, process]
      --wasm-dir <DIR>     Take the contracts from here instead, e.g. the CI contracts-wasm artifact (also CARAVEL_WASM_DIR)
      --list               List the templates instead
      --var <NAME=VALUE>   Set one of the lane file's vars; repeat for more. Read by the var's type (lists and maps as TOML: --var 'validators=["1","2"]'). Also CARAVEL_VAR_<name>
      --var-file <FILE>    A TOML file of var values (name = value); later files win, and --var over them
  -h, --help               Print help