1. Start detached
up -d builds (if needed) and starts the whole stack in the background.
docker compose up -dTyporithm · easy
Step 1 of 8 · intro card
Compose
docker compose up -d starts the whole stack detached, ps and logs inspect it, and down tears it down — adding -v also removes named volumes. This is the everyday local-dev loop.
docker compose up -d brings the entire stack up in the background, building images first if they are missing. Drop -d to stream all logs in the foreground.
docker compose ps lists the running services with their state and ports, and docker compose logs -f web follows one service's output live so you can watch it work.
docker compose down stops and removes the containers and the default network; adding -v also removes named volumes (deleting their data). build and pull refresh images, and up --scale runs multiple replicas of a service.
up -d starts the stack detached.
ps and logs -f inspect running services.
down -v removes containers and named volumes.
docker compose up -d
docker compose ps
docker compose logs -f web
docker compose down -vConnect each part of the code to the concept before you type.
up -d builds (if needed) and starts the whole stack in the background.
docker compose up -dps shows each service's container, state, and published ports.
docker compose pslogs -f web streams the web service's output live, like tail -f.
docker compose logs -f webdown stops and removes containers and networks; -v also deletes named volumes.
docker compose down -v-f follows the stream and web limits output to that one service.
-f webRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.