docker-dev

Automate Docker dev environment setup by orchestrating multiple services with docker-compose. This lifecycle management handles start, stop, restart, and status actions for your local containers, ensuring a consistent stack.

View logs and troubleshoot containers by executing the logs action within your docker-compose stack. This lifecycle management capability allows you to monitor service output and diagnose issues across your orchestrated environment.

Yes, you can include tools like pgadmin, redis-commander, mailhog, and minio by enabling optional profiles. Use flags such as --tools, --mail, or --storage to bootstrap a local development environment with these specific services.

Yes, docker and docker-compose are required dependencies to orchestrate your dev environment. The automation requires docker-compose files located under the docker-compose directory to manage the container stack lifecycle.

The default behavior when no action is provided to the Docker dev environment orchestration is to return the status. This allows you to quickly check the current state of your orchestrated local containers.

Clean and reset a local Docker development environment by running the clean action. This lifecycle management feature removes stopped containers and clears the orchestrated stack to prepare for a fresh bootstrap.