stackblaze init
Creates a pipeline and writes .stackblaze/project.json in the current directory, linking it to that pipeline and phase. If a pipeline with that name already exists, it is linked instead. Alias: stackblaze new.
stackblaze init [options]Options
Section titled “Options”| Flag | Description |
|---|---|
-p, --pipeline <name> |
Pipeline name (default: the directory name) |
--phase <name> |
Phase to link (default: the first of --phases, else production) |
--phases <names...> |
Phases to create on a new pipeline (default: production) |
--domain <host> |
Wildcard domain for the new pipeline |
-y, --yes |
Accept the defaults without prompting |
Also accepts --token, --api-url, -o, --output and --json.
In a terminal, init asks for the pipeline and phase names unless you pass --pipeline or -y.
Examples
Section titled “Examples”stackblaze initstackblaze init -ystackblaze init --pipeline shop --phases staging production --phase stagingNext: stackblaze up. init does not link an app; up adds it.