commit 1852175906c5f9940331f1806e5fb7694da736aa
parent f3e87ba8325585293aed316884451216c66d32a6
Author: tobi <31960611+tsmethurst@users.noreply.github.com>
Date: Thu, 17 Nov 2022 13:40:05 +0100
[docs] Update docker.md with docker tag / version stuff (#1067)
Diffstat:
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/docs/installation_guide/docker.md b/docs/installation_guide/docker.md
@@ -60,11 +60,15 @@ nano docker-compose.yaml
#### Version
-First, you should update the GoToSocial version number to the latest stable release.
+If desired, update the GoToSocial Docker image tag to the version of GtS you want to use.
-The list of releases can be found [right here](https://github.com/superseriousbusiness/gotosocial/releases), with the newest release at the top.
+`latest` - the default. This points to the latest stable release of GoToSocial.
-Replace `latest` in the docker-compose.yaml with the number of the release (without the leading `v` or trailing version name). So for example if you want to run [v0.3.1 Sleepy Sloth](https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.3.1) you should replace:
+`snapshot` - points to whatever code is currently on the main branch. Not guaranteed to be stable, will often be broken. Use with caution.
+
+You can also replace `latest` with a specific GoToSocial version number. This is recommended when you want to make sure that you don't update your GoToSocial version by accident, which can cause problems.
+
+The list of releases can be found [right here](https://github.com/superseriousbusiness/gotosocial/releases), with the newest release at the top. Replace `latest` in the docker-compose.yaml with the number of the desired release (without the leading `v` or trailing version name). So for example if you want to run [v0.3.1 Sleepy Sloth](https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.3.1) for whatever reason, you should replace:
```text
image: superseriousbusiness/gotosocial:latest
