From e861e149c06c2fd2aee5d4ff024343409b1621c7 Mon Sep 17 00:00:00 2001 From: Brandon <61758877+wood-brandon@users.noreply.github.com> Date: Tue, 23 Dec 2025 15:48:04 +1300 Subject: [PATCH] fix: docker run uses `--env` --- docs/docker-deployment.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docker-deployment.md b/docs/docker-deployment.md index 03b4d9c8b..bc0ff0f04 100644 --- a/docs/docker-deployment.md +++ b/docs/docker-deployment.md @@ -45,7 +45,7 @@ bin/rails secret Once you have one, set it in the `SECRET_KEY_BASE` environment variable: ```sh -docker run --environment SECRET_KEY_BASE=abcdefabcdef ... +docker run --env SECRET_KEY_BASE=abcdefabcdef ... ``` #### SSL @@ -56,7 +56,7 @@ Note that if you're using SSL, you'll want to allow traffic on ports 80 and 443. So if you were running on `fizzy.example.com` you could enable SSL like this: ```sh -docker run --publish 80:80 --publish 443:443 --environment TLS_DOMAIN=fizzy.example.com ... +docker run --publish 80:80 --publish 443:443 --env TLS_DOMAIN=fizzy.example.com ... ``` If you are terminating SSL in some other proxy in front of Fizzy, then you don't need to set `TLS_DOMAIN`, and can just publish port 80: @@ -67,7 +67,7 @@ docker run --publish 80:80 ... If you aren't using SSL at all (for example, if you want to run it locally on your laptop) then you should specify `DISABLE_SSL=true` instead: ```sh -docker run --publish 80:80 --environment DISABLE_SSL=true ... +docker run --publish 80:80 --env DISABLE_SSL=true ... ``` #### SMTP Email @@ -96,7 +96,7 @@ Fizzy needs to know the public URL of your instance so it can generate correct l Set `BASE_URL` to the full URL where your Fizzy instance is accessible: ```sh -docker run --environment BASE_URL=https://fizzy.example.com ... +docker run --env BASE_URL=https://fizzy.example.com ... ``` #### VAPID keys