refactor: Update docker-compose commands to use "docker compose" inst…

…ead of "docker-compose"

.github/workflows/test-release.yaml

@@ -1067,7 +1067,7 @@ jobs:
       - name: Wait for server to start
         run: bash ./Tests/Scripts/status-check.sh http://localhost
       - name: Run E2E Tests. Run docker container e2e in docker compose file
-        run: export $(grep -v '^#' config.env | xargs) && docker-compose -f docker-compose.dev.yml up --exit-code-from e2e --abort-on-container-exit e2e || (docker-compose -f docker-compose.dev.yml logs e2e && exit 1)
+        run: export $(grep -v '^#' config.env | xargs) && docker compose -f docker-compose.dev.yml up --exit-code-from e2e --abort-on-container-exit e2e || (docker compose -f docker-compose.dev.yml logs e2e && exit 1)
       - name: Upload test results
         uses: actions/upload-artifact@v4
         # Run this on failure
@@ -1120,7 +1120,7 @@ jobs:
       - name: Wait for server to start
         run: bash ./Tests/Scripts/status-check.sh http://localhost
       - name: Run E2E Tests. Run docker container e2e in docker compose file
-        run: export $(grep -v '^#' config.env | xargs) && docker-compose -f docker-compose.dev.yml up --exit-code-from e2e --abort-on-container-exit e2e || (docker-compose -f docker-compose.dev.yml logs e2e && exit 1)
+        run: export $(grep -v '^#' config.env | xargs) && docker compose -f docker-compose.dev.yml up --exit-code-from e2e --abort-on-container-exit e2e || (docker compose -f docker-compose.dev.yml logs e2e && exit 1)
       - name: Upload test results
         uses: actions/upload-artifact@v4
         # Run this on failure

App/FeatureSet/Docs/Content/copilot/deploy-llm-server.md

@@ -48,7 +48,7 @@ llm:
 Run the following command to start the LLM Server:
 
 ```bash
-docker-compose up -d
+docker compose up -d
 ```
 
 You can now access the LLM Server at `http://localhost:8547`. 

App/FeatureSet/Docs/Content/installation/docker-compose.md

@@ -49,7 +49,7 @@ npm start
 If you don't like to use npm or do not have it installed, run this instead: 
 
 ```
-# Read env vars from config.env file and run docker-compose up.
+# Read env vars from config.env file and run docker compose up.
 (export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d)
 
 # Use sudo if you're having permission issues with binding ports. 

App/FeatureSet/Docs/Content/probe/custom-probe.md

@@ -38,7 +38,7 @@ services:
 Then run the following command:
 
 ```
-docker-compose up -d
+docker compose up -d
 ```
 
 If you are self hosting OneUptime, you can change `ONEUPTIME_URL` to your custom self hosted instance.

Haraka/README.md

@@ -38,7 +38,7 @@ bash generate.sh
 cd ..
 ```
 
-`public` and `private` files should have been generated inside of `dkim` folder. Please also add DNS and env vars to docker-compose files. Values of that should be shown on the console.
+`public` and `private` files should have been generated inside of `dkim` folder. Please also add DNS and env vars to docker compose files. Values of that should be shown on the console.
 
 
 

config.example.env

@@ -53,7 +53,7 @@ ENVIRONMENT=production
 # What image should we pull from docker hub. This only applies when the ENVIRONMENT is production or test
 APP_TAG=release
 
-# What is the name of the docker-compose project. This is used to prefix the docker containers.
+# What is the name of the docker compose project. This is used to prefix the docker containers.
 COMPOSE_PROJECT_NAME=oneuptime
 
 # OTEL HOST - if you like the collector to be hosted on a different server then change this to the IP of the server.