product:down

Introduction

product:down stops your product and the stacks of its features. Without a flag it stops production when production is running, and development otherwise.

splent product:down

🛑  my_first_app: stopped successfully
🛑  splent_io/splent_feature_cache@v1.5.6: stopped successfully
🛑 Development environment stopped.

Only this product’s stacks are stopped, so another product’s containers are never touched.

---

Stopping one environment

splent product:down --dev
splent product:down --prod

--dev stops the project <product>_dev and every feature stack of features plus features_dev.

--prod stops the deployment product:deploy started from deploy/ (project <product>_deploy), and the stacks product:up --prod started (<product>_prod and its feature stacks).

---

Removing the volumes

splent product:down --prod --v

--v also removes the volumes of the product and its features, after one question that names the projects. It is spelled with two dashes.

Remove the volumes of the PRODUCTION deployment my_first_app_deploy and my_first_app_prod (database, uploads)?

This deletes the database and the uploads. Without a flag, --v applies to production when production is running, and the command says so first.

---

Reference

Options

Option	Description
--dev	Stop development
--prod	Stop production, the deployment and the stacks product:up --prod started
--v	Also remove the volumes, after a confirmation

Errors

Message	Meaning
<name>: 'docker compose down' failed (exit N).	The other stacks are still stopped. The command ends with N stack(s) did not stop: <names>. and exits 1
No production stack found for <product>: ...	Neither deploy/docker-compose.yml nor docker/docker-compose.prod.yml exists. Nothing is stopped
⚠️ pyproject.toml not found.	Only the product’s own stack is stopped

---

Requirements

• A selected product (SPLENT_APP).
• Docker running, checked before anything stops.