diff options
author | fox <[email protected]> | 2020-09-21 17:48:20 +0000 |
---|---|---|
committer | fox <[email protected]> | 2020-09-21 17:48:20 +0000 |
commit | 4f084cd42f1698009c1e3222b98bfa10ff98e8f9 (patch) | |
tree | f2373ab9f942d9967af5bbdb1842b264bfa55c60 /InstallationNotes.md | |
parent | ec3a8c1961ab513558f4e3b83ab980ddb142e545 (diff) |
Update page 'InstallationNotes'
Diffstat (limited to 'InstallationNotes.md')
-rw-r--r-- | InstallationNotes.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/InstallationNotes.md b/InstallationNotes.md index abf5ea1..8ec2d8a 100644 --- a/InstallationNotes.md +++ b/InstallationNotes.md @@ -4,7 +4,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 updated automatically
+### 1. Dynamic: tt-rss is updated automatically
Use this if you want to always run latest tt-rss code.
@@ -12,7 +12,7 @@ Use this if you want to always run latest tt-rss code. Updates are applied automatically from git master branch on container restart.
-#### 2. Static: uses pre-built images provided via Docker Hub
+### 2. 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).
|