Give the compose stack an explicit project name

Compose derives the project name from the directory holding the file, which here is 'docker'. Anything else on the same host that keeps its compose file in a subdirectory of that name joins the same project, and a 'docker compose down' in either directory then stops both. That happened on the machine this is deployed to: a second stack's database container was registered under the same project as this dashboard, and running up -d here reported that stack's containers as orphans.

Fixing only the deployment would have left this shipped to anyone who clones the repo, since they get the same directory name.

Author: scaso01

docker/docker-compose.yml

@@ -1,3 +1,12 @@
+# Without this, Compose names the project after the directory holding this
+# file, which is "docker". Any other project that also keeps its compose file
+# in a subdirectory called "docker" then lands in the same project, and
+# `docker compose down` in either one tears down both. That is not
+# hypothetical: it happened on the machine this is deployed to, where a second
+# stack's database container was registered under the same project as this
+# dashboard.
+name: quant-tools
+
 services:
   dashboard:
     image: quant-tools-dashboard:latest