I use the linuxserver one Docker. The main reason is becuase it puts the main config as a mounted volume, so it exposes directories for local_plugins and local_themes.
The main issue with a generic container is if you want to load plugins, ie I used to use the feedly theme so needed a container than incorporated that as part of the build…the linux server container doesn’t have that problem as I can keep the theme locally.
I don’t have the ngnix as I use caddy elsewhere to point at my tt-rss instance, but do have the container and postgres (and not included here is rss-bridge)
yeah stuff exposed via docker volumes is definitely a must.
to add to the requirements in the first post: container should skip initial installation steps and install default schema to linked database server and matching config.php on creation so things would be ready out of the box.
I believe the linuxserver one did this for me, standing it up was via opml import which is pretty fine for that purpose…the only thing that breaks is the id of feeds must change and it breaks your filters.
i’ve looked over the linuxserver one and it involves too much manual configuration for my taste. i guess this works if you want to get into details but i would prefer a compose solution working OOTB which i could push into the installation guide to make it easier for people who would want things to just work.
i mean this container installation involves creating the database yourself and editing nginx configuration manually, at this point you might as well do everything else yourself. something like that would be a very questionable improvement over current installation process outlined in the guide.
e: if nothing else their installation-related page is several times longer than our guide.
Hmm, I don’t think I’ve ever done that…and I don’t think I re-used a db from another container (I may have tried and failed). So just did an import as I mentioned.
yeah I have that, you can see in my compose the postgres container and the tt-rss container…but I didn’t have to run anything special on first run to create the db.
Hi all, first of all, I love this utility. TT-rss is hosted in my home “server” and I am all day connected to eat for personal and business purposes. I am technology fun, so I would like to migrate to ttss dockerized, however, as per my understanding, this utility works only with docker-compose? I have a google apps kubernets and I am wondering if I can deploy it there as a cluster.
I am waiting a new server from my university, I will try to install first docker as per your instructions, in order to understand exactly how it works, and after that I will try in google cloud with kubernets. I let you know asap.