public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-24 23:22:58 +00:00
Code Issues Releases Wiki Activity

Add comments

Browse Source
This commit is contained in:
David Young
2017-12-12 21:22:27 +13:00
parent 7089e7194e
commit ddf44abed9
26 changed files with 71 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
manuscript/recipies/tiny-tiny-rss.md
View File

@@ -134,3 +134,5 @@ There are several TTRSS containers available on docker hub, none of them "offici
1. Docker swarm looses the docker-compose concept of "dependencies" between containers. In the case of this stack, the application server typically starts up before the database container, which causes the database autoconfiguration scripts to fail, and brings up the app in a broken state. To prevent this, I include "[wait-for](https://github.com/Eficode/wait-for/)", which (combined with "S6_BEHAVIOUR_IF_STAGE2_FAILS=2"), will cause the app container to restart (and attempt to auto-configure itself) until the database is ready.
2. The upstream git URL [changed recently](https://discourse.tt-rss.org/t/gitlab-is-overbloated-shit-garbage/325/6), but my experience of the new repository is that it's **SO** slow, that the initial "git clone" on setup of the container times out. To work around this, I created [my own repo](https://github.com/funkypenguin/tt-rss.git), cloned upstream, pushed it into my repo, and pointed the container at my own repo with TTRSS_REPO. I don't get the _latest_ code changes, but at least the app container starts up. When upstream git is performing properly, I'll remove TTRSS_REPO to revert back to the "rolling release".
## Your comments?