Check: Compose | ComputeSphere Learn

Goal: Confirm you can read a Compose file, run and tear down a stack, and decide what goes to ComputeSphere.

Four questions: three on this module, one from Module 4. Every answer explains itself, right or wrong.

In compose.yaml, web connects to postgres://app:demo-password@db:5432/app. You rename the db service to database. What else must change?The passwordThe host in DATABASE_URL, and the depends_on entryNothing: Compose updates the hostname for you

You want to stop the stack for the night and keep the database's rows. Which command?docker compose downdocker compose down -vdocker compose up --build

csph import compose warns: PostgreSQL imported as a plain container. What's the right fix on ComputeSphere?Switch the service to a managed database in the consoleDeploy it anyway; the data survives redeploysHost the database elsewhere and give the app its connection string as a secret

From Module 4: docker compose up --build builds web from ./app, and the image turns out to contain your .env file and your laptop's node_modules. What fixes it?A .dockerignore in ./app listing .env and node_modulesBuild with docker build instead of ComposeRUN rm -rf .env node_modules at the end of the Dockerfile

Retry as often as you like.