From 8a5c0c931d1f5164dc19174c67360bbb83b9adb5 Mon Sep 17 00:00:00 2001 From: GershN Date: Wed, 3 Jun 2026 11:01:42 +0100 Subject: [PATCH 1/3] Update docker-deployment.md --- docs/docker-deployment.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/docker-deployment.md b/docs/docker-deployment.md index c74efe2915..18ee654211 100644 --- a/docs/docker-deployment.md +++ b/docs/docker-deployment.md @@ -52,7 +52,7 @@ docker run --env SECRET_KEY_BASE=abcdefabcdef ... If you want the Fizzy container to handle its own SSL automatically, you just need to specify the domain name that you're running it on. You can do that with the `TLS_DOMAIN` environment variable. -Note that if you're using SSL, you'll want to allow traffic on ports 80 and 443. +Note that if you're using SSL, you'll want to allow traffic on ports 80 and 443 and allow access from the internet. So if you were running on `fizzy.example.com` you could enable SSL like this: ```sh @@ -70,6 +70,8 @@ If you aren't using SSL at all (for example, if you want to run it locally on yo docker run --publish 80:80 --env DISABLE_SSL=true ... ``` +The TLS_domain setting uses Thunder and LetsEncrypt to automatically provide SSL/TLS access (https://github.com/basecamp/thruster) + #### SMTP Email Fizzy needs to be able to send email for its sign up/sign in flow, and for its regular summary emails. From 1539caf6f4cbcc885b12a95c216f00538be08bb5 Mon Sep 17 00:00:00 2001 From: GershN Date: Wed, 3 Jun 2026 11:19:30 +0100 Subject: [PATCH 2/3] Copilot review suggested change to Update docker-deployment.md capitalise TLS_DOMAIN --- docs/docker-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docker-deployment.md b/docs/docker-deployment.md index 18ee654211..431acc4471 100644 --- a/docs/docker-deployment.md +++ b/docs/docker-deployment.md @@ -70,7 +70,7 @@ If you aren't using SSL at all (for example, if you want to run it locally on yo docker run --publish 80:80 --env DISABLE_SSL=true ... ``` -The TLS_domain setting uses Thunder and LetsEncrypt to automatically provide SSL/TLS access (https://github.com/basecamp/thruster) +The TLS_DOMAIN setting uses Thunder and LetsEncrypt to automatically provide SSL/TLS access (https://github.com/basecamp/thruster) #### SMTP Email From 1966af159c144b2cacfc1d7711d68b337cb55ea5 Mon Sep 17 00:00:00 2001 From: GershN Date: Wed, 3 Jun 2026 11:21:40 +0100 Subject: [PATCH 3/3] Typo fix Update docker-deployment.md typo Thruster not Thunder. --- docs/docker-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docker-deployment.md b/docs/docker-deployment.md index 431acc4471..31f058d69d 100644 --- a/docs/docker-deployment.md +++ b/docs/docker-deployment.md @@ -70,7 +70,7 @@ If you aren't using SSL at all (for example, if you want to run it locally on yo docker run --publish 80:80 --env DISABLE_SSL=true ... ``` -The TLS_DOMAIN setting uses Thunder and LetsEncrypt to automatically provide SSL/TLS access (https://github.com/basecamp/thruster) +The TLS_DOMAIN setting uses Thruster and LetsEncrypt to automatically provide SSL/TLS access (https://github.com/basecamp/thruster) #### SMTP Email