Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/docker-deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 Thruster 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.
Expand Down