Rename docker-compose.yml to compose.yaml

.devcontainer/devcontainer.json

@@ -1,11 +1,11 @@
 // For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
 // https://github.com/microsoft/vscode-dev-containers/tree/v0.163.1/containers/docker-existing-docker-compose
-// If you want to run as a non-root user in the container, see .devcontainer/docker-compose.yml.
+// If you want to run as a non-root user in the container, see .devcontainer/compose.yaml.
 {
     "name": "Existing Docker Compose (Extend)",
     "dockerComposeFile": [
-        "../docker-compose.yml",
+        "../compose.yaml",
-        "docker-compose.yml"
+        "compose.yaml"
     ],
     "service": "web",
     "workspaceFolder": "/code",

.dockerignore

@@ -4,6 +4,7 @@
 **/node_modules
 **/Dockerfile
 **/docker-compose.yml
+**/compose.yaml
 **/Procfile
 **/Vagrantfile
 **/.devcontainer

README.md

@@ -64,7 +64,7 @@ WARNINGS:
 If you're running this on Linux you might get into some privilege issues that can be solved using this command (tested on Ubuntu):
 
 ```sh
-CURRENT_UID=$(id -u):$(id -g) docker compose -f docker-compose.yml -f docker-compose.linux.yml up
+CURRENT_UID=$(id -u):$(id -g) docker compose -f compose.yaml -f compose.linux.yaml up
 ```
 
 Alternatively, if you're using VSCode and have the "Remote - Containers" extension, you can open the command palette and select "Remote Containers - Reopen in Container" to attach VSCode to the container. This allows for much deeper debugging.