mirror
/
sitespeed.io
mirror of https://github.com/sitespeedio/sitespeed.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: use stable versions

This commit is contained in:
soulgalore 2024-12-25 16:10:41 +01:00
parent 4abdde0efb
commit 1b009d2f69
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/documentation/sitespeed.io/docker/index.md
View File

@ -110,6 +110,16 @@ docker pull sitespeedio/sitespeed.io:X.Y.Z
Then change your start script (or where you start your container) to use the new version number.
You can also pin sitespeed.io to stable versions. Say for example that you want to pin your version to version 35. Then you can use the following version:
```bash
docker pull sitespeedio/sitespeed.io:35
```
Then when we continously release new 35 version, you can just run `docker pull sitespeedio/sitespeed.io:35` and you will get the latest released version of 35.
## Tags and version
In the real world you should always specify the exact version (tag) of the Docker container to make sure you use the same version for every run. If you use the latest tag you will download newer version of the container as they become available, meaning you can have major changes between test runs (version upgrades, dependencies updates, browser versions, etc). So you should always specify a tag after the container name(X.Y.Z). This is important for sitespeed.io/browsertime/Graphite/Grafana containers. It's important for all containers you use. Never use the *latest* tag!