Sandbox Manager

You can provision an Ignition sandbox by running the CLI command to create a new environment with a specified name and port. The Skill uses a Docker Compose template with configurable settings to ensure consistent startup and health validation.

Managing Ignition gateway lifecycle involves using a deterministic CLI interface to execute repeatable operations like create, status, reset, and teardown across multiple sandboxes to maintain clean development environments.

Yes, you can configure the port, version, and edition when creating an Ignition sandbox. The Docker Compose template supports these configurable parameters along with built-in health checks to ensure readiness.

Checking Ignition gateway status involves using the CLI to monitor container status and gateway health. This ensures the sandbox is fully ready and operational before you begin development or testing.

Yes, Docker is required to run Ignition sandbox operations. The Skill relies on Docker Compose to provision containers, apply configurable health checks, and manage the complete startup and teardown lifecycle.

Accessing gateway logs for debugging uses the CLI interface to retrieve container output. This observability feature allows you to validate startup behavior and troubleshoot errors within your isolated Ignition environment.