diff options
| author | fox <[email protected]> | 2020-09-21 10:52:15 +0000 |
|---|---|---|
| committer | fox <[email protected]> | 2020-09-21 10:52:15 +0000 |
| commit | 8e915656f53154c317d550b69e333bc6d3cc2418 (patch) | |
| tree | 1db2ec99622320149d677ff27f90238a15379c77 | |
| parent | bbc8acc0ee90286aff1b9ce5d8c46b2491ba98e0 (diff) | |
Update page 'InstallationNotes'
| -rw-r--r-- | InstallationNotes.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/InstallationNotes.md b/InstallationNotes.md index f7d2883..94eb366 100644 --- a/InstallationNotes.md +++ b/InstallationNotes.md @@ -8,7 +8,7 @@ As of 2020, the recommended way to deploy tt-rss is via Docker. Unless you have Official dockerized setup uses [docker-compose](https://docs.docker.com/compose/). There are two variants available:
-#### 1. Dynamic: tt-rss is automatically updated on container (re)start
+#### 1. Dynamic: tt-rss is updated automatically
Use this if you want to always run latest tt-rss code.
@@ -18,7 +18,7 @@ Updates are applied automatically from git master branch on container restart. #### 2. Static: uses pre-built images provided via Docker Hub
-This seems to be a more commonly used pattern for Docker containers: images (including 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 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.
|