summaryrefslogtreecommitdiff
path: root/InstallationNotes.md
diff options
context:
space:
mode:
authorfox <[email protected]>2020-10-11 06:22:52 +0000
committerfox <[email protected]>2020-10-11 06:22:52 +0000
commitb539ea1b6eb15a4e15c28c1b1a60f9e63e2e9f14 (patch)
tree7465b5c2e6f146676da50fda985387ca40e70c15 /InstallationNotes.md
parent63550a7b80b9273de746788f6fb779b2dd84a698 (diff)
Update page 'InstallationNotes'
Diffstat (limited to 'InstallationNotes.md')
-rw-r--r--InstallationNotes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/InstallationNotes.md b/InstallationNotes.md
index aecc7d9..0c8c0c9 100644
--- a/InstallationNotes.md
+++ b/InstallationNotes.md
@@ -4,7 +4,7 @@ As of 2020, Docker is the recommended way to deploy tt-rss. Unless you have very
### Static: uses pre-built images provided via Docker Hub
-This seems to be a more commonly used pattern for Docker containers: images (including a snapshot of tt-rss source code) are built automatically and then pushed to [Docker Hub](https://hub.docker.com/u/cthulhoo).
+This seems to be a more commonly used pattern for Docker containers: images (including a snapshot of tt-rss source code) are built automatically on master branch update and then pushed to [Docker Hub](https://hub.docker.com/u/cthulhoo).
Use this if you want manual control over tt-rss updates or an ability to revert to an older prebuilt image.