mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2024-11-24 09:20:59 +00:00
[docs] Update docker.md with docker tag / version stuff (#1067)
This commit is contained in:
parent
f3e87ba832
commit
1852175906
1 changed files with 7 additions and 3 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue