As of 2022, I recommend everyone to use Docker Hub images. Those are generated through a proper CI/CD pipeline which involves basic unit tests and static code analysis. This means you’re less likely to receive a broken image. You get no such guarantees when using git master branch. You won’t be able to easily rollback to an earlier image either.
Docker(-compose) is the only supported way to deploy tt-rss.
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 updates and - if build succeeds - pushed to Docker Hub.
This is recommended for users.
Updates are handled the usual way. Either run docker-compose pull etc. when appropriate or use something like Watchtower to apply updates automatically.
Use this if you want to always run latest tt-rss code and/or don’t want to rely on Docker Hub. Also, using dynamic image makes more sense for development.
→ Installation guide (dynamic)
Updates are applied automatically from git master branch on container restart.
See also: Host installation (not supported).
Sun Jun 18 03:25:02 UTC 2023