dde

To run local Docker development commands safely, use a project-aware CLI that detects a `.dde/config.yml` file and routes all project-dependent actions through `dde project:exec` commands, preventing unsafe host execution. This ensures commands run inside the correct isolated containers.

The best way to manage Docker container lifecycle is by using `dde project:*` commands to start, stop, rebuild, update, and inspect isolated project environments. This provides reliable lifecycle management for both system services and per-project containers with options for hooks and forced rebuilds.

To get separate database instances for Git worktrees, the CLI automatically rewrites database URLs for each worktree, ensuring they receive unique hostnames and TLS contexts. This allows you to use DB shells, export/import, and snapshots safely within isolated worktree environments.

Yes, this Docker workflow tool supports HTTPS and local DNS configuration to make your application reachable at the correct `.test` URL. It handles local DNS and TLS context automatically when you start the project environment using `dde project:up`.

Yes, you can get JSON output from Docker container logs and status commands. The CLI supports JSON output across its lifecycle, system, database, and project execution subcommands, allowing you to programmatically parse container states and log data.

Commands accidentally execute on the host when local development workflows lack project-aware orchestration. By requiring a `.dde/config.yml` file and directing actions through `dde project:exec`, the CLI ensures all project-dependent tasks are container-bound, preventing unsafe host execution.