canasta start

Start a Canasta instance

Synopsis

Start the Docker containers for a Canasta instance. Before bringing the stack up, COMPOSE_PROFILES in .env is reconciled from the instance's feature flags so optional components start or stay down based on their current setting:

CANASTA_ENABLE_VARNISH (default true) — Varnish cache
CANASTA_ENABLE_OBSERVABILITY (default false) — OpenSearch, Logstash and OpenSearch Dashboards log stack
CANASTA_ENABLE_ELASTICSEARCH (default false) — Elasticsearch

If the instance has development mode enabled, Xdebug starts automatically. Use canasta devmode enable or canasta devmode disable to toggle development mode; use canasta config set <FLAG>=true|false to adjust the optional components.

The command returns once the web container reports healthy, so a command run immediately afterward does not race the image's startup. An image that declares no healthcheck is not waited on. If the web container's startup composer update failed, so the packages in config/composer.local.json are not installed, a warning names the failure and how to read its details.

canasta start [flags]

Examples

canasta start

Flags

Flag	Shorthand	Description	Default	Required	Orchestrator
`--id`	`-i`	Canasta instance ID	*		Both

* Defaults to the Canasta instance matching the current directory, if any.

Global flags

Flag	Shorthand	Description	Default	Required	Orchestrator
`--help`	`-h`	Show help message and exit			Both
`--verbose`	`-v`	Enable verbose output			Both