Stack v0.2.0 — optional services

Keep occasional development services available in the dashboard without starting them on every launch.

Optional services

• Set autostart = false in a service block to leave it visibly inactive at launch. Inactive services do not lower stack health.
• Select an inactive or stopped service and press s to start it and its required dependencies. Press s again after a failed start to retry.
• Requested services use the existing port allocation, readiness checks, logs, health monitoring, and shutdown handling.
• Automatic services still start all their required dependencies, including optional dependencies.
• auto_restart = true leaves optional services inactive until requested. After activation, normal crash recovery applies.
• Each new stack session resets optional services to inactive unless an automatic service needs them.

Resolves #1.

Upgrade

Existing configurations require no changes. Services start automatically when autostart is omitted.

brew update
brew upgrade caliluke/stack/stack

For a first installation:

brew install caliluke/stack/stack

Validation

Go tests, race detection, vet, and build checks pass. Regression coverage includes dependency retries, shared dependencies, port reassignment, Compose startup, crash recovery, and shutdown cleanup. TUI snapshots cover inactive, waiting, and failed states at multiple terminal sizes. Version and help output are checked without starting services.