TDK CLI Core: Run Your Whole Local Stack With One Command
Every multi-service project has the same morning. You pull the latest code, start the database, start the API, start the frontend, start the worker, and hope the ports line up. Something is always out of order. TDK CLI Core is built to make that one command: tdk up . What the command does tdk up reads the project's service.json files, works out which services exist and what they depend on, and…
The TDK CLI Core simplifies the process of setting up multi-service projects with a single command. Instead of manually starting each service such as the database, API, frontend, and worker, developers can run a single command: "tdk up". This command reads the project's service.json files to determine which services exist and their dependencies, starting them in the correct order. Services that rely on others wait until those services are up and running.
Shared infrastructure like Postgres and the Traefik proxy are started with the services. If the default Postgres port is in use, TDK chooses a different, available port from a predetermined range and informs the user of the chosen port. The user can also override these settings using environment variables.
It's often not necessary to start all services. The command "tdk up --only service" allows starting individual services along with their dependent services. The names provided must belong to the same stack, and dependencies may extend across different stacks.
Before initiating the start, TDK offers a "dry run" feature by executing "tdk up main --dry-run". This command previews the services that will run, their health check URLs, the allocated ports, and the exact Tilt command that will be executed. This allows developers to review the plan before any containers are actually started.
If the command fails to start the stack, developers can first run "tdk doctor --json" to diagnose the issue. This command provides information on the host type, whether the container runtime is accessible, and if the stack can be started. If "canUp" is false, the project's structure itself is likely at fault. However, if the stack starts but individual services fail, running "tdk logs --json --service name" shows recent log entries for the problematic service, and "tdk status --json" displays readiness and any failures.
In summary, TDK CLI Core streamlines the usual morning routine of launching a multi-service project into a single command, handling dependencies, ports, and providing a dry run for verification. The checks are conducted first, ensuring any problems are identified prior to the actual container startup.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
