Docker & Tiny Tiny RSS sorted finally

TTRSS Php error

I have had on my task list for a long time to fix two problems with my Tiny Tiny RSS setup.

  1. Fix the problem I’m having connecting to TTRSS in a browser since a upgrade
  2. Sort out a decent RSS reader for Ubuntu

Originally it was working fine then a upgrade broke the web interface for me and many others. The confusing and joyful thing for me, was any application which talked to the API was unaffected. Meaning my Android clients were fine including the one on my eink tablet. However all the RSS clients on Ubuntu would either not connect to ttrss, were generally rubbish or wouldn’t work in later versions of Ubuntu (like RSS Owl). The advice seemed to point to using a browser extention.

The first problem was something to do with the PHP which seemed pretty easy to fix but all the solutions assumed you were running it all on a standard webserver and had control over everything. Of course I was running it within Docker and had no idea where config.php was or even where docker had installed anything.

After actually sitting down and looking around my server as a sudo not myself (its the first time I actually dedicated time to do), I found the Docker install and learned what docker was actually doing. My ttrss docker image is actually located under /var/lib/docker/aufs/mnt/{random hash}/var/www/ttrss/.

Under that I could find the config.php file and make changes so it was only accessible over my Vpn connection – yeah, I thought this was very clever but maybe obvious to everyone else. So the only way to hit the web front end of my ttrss install is via my Vpn but API calls are done without the Vpn.

As I found the root of ttrss, I was also able to finally install feedreader which is hightly rated by many. The problem I’ve always had is feedreader complained that it needed a certain plugin installed under ttrss’s plugin directory, which previously I couldn’t find to install. Of course now I know where it is and could copy it there, I was very pleased with myself. Next stop¬†brunch at Ezra & Gil and wait for Feedreader to pull down full text for 8500+ items.

Tiny tiny RSS experience a week later?

I have had quite a bit of feedback from my post about moving away from Feedly to a self hosted solution called Tiny Tiny RSS.

Some interesting questions have emerged from people and to be fair it certainly deserves a follow up.

I made my instance of¬†TT-RSS available on the public netw,¬†because I didn’t see the point of installing my VPN software on my eink reader.¬†I also installed the official TT-RSS app which is a 7 day trail before you buy the full version for 4 pounds.¬†I haven’t bought the full version yet because the¬†app doesn’t seem to work well¬†when offline? It would be great if the app understood if the device¬†was offline and automaticilly disabled the update feeds option. It currently doesn’t seem to do this well… I much prefer Greader for this, but ttrss app isn’t far behind.

Simon commented he paid for Feedly because of the IFTTT options, but it seems weird to pay for this  because you can easily turn most of TT-RSS into a another feed and IFTTT has a RSS option which you can use to trigger most things. This reminds me of my work along while back about pipelines.

Because of this, I have been thinking about feeding Greader with the RSS from my TTRSS install. The only real disadvantage is nothing would be synced to the server? This is also something I’ve been thinking about with a linux desktop reader like thunderbird because I can’t seem to install a TTRSS reader which works.

I tried a few but each has had problems.

Feed the Moneky looked very promising but when I finally get the appimage loaded, it shows nothing? Feedreader looked great and after finally getting flatpak working, I’m faced with the error that I need to install the api-feedreader plugin in my TTRSS server. How I do this when I’m using docker is a question I have no answer for, except it seems I need to use another docker container?

So generally its going well but hitting a few points which need straighing out. It would be so useful to compile supported applications into a wiki page.

Oh I found this useful when understanding about appimages, snap, flatpak, etc.

Host your own RSS aggregator?

hosting Tiny Tiny RSS

It started with me getting fed up with Feedly trying to up-sell me to their premium subscription. I mean I get it but $5/month to host a simple RSS aggregator? This seems quite a hefty price (even with all the extras it provides, which I never really use).

So I first looked for alternatives to Feedly and found quite a lot. The main thing for me was having a Sync API, so I’m not reading the same stuff across my different devices. My thought was with a standard API, it wouldn’t matter what client or platform I use (although I’m using Linux and Android mainly). Standard I thought… boy was I dreaming.

After a lot of looking and reading I said screw this, I’m self hosting my own copy of tiny tiny rss, which seems very popular with people like myself trying to do the same thing. It seemed quite straight forward and I decided it was time to give rkt or docker a try as there was a docker image for it.

In a evening I had it setup, running and working with my exported feedly OPML file, while watching a film and cooking. Its currently only available to my network but I’ll likely make it externally available (without my VPN) once I got it setup with a SSL cert and 2 factor auth. I did notice my fav RSS reader on Android did support ttrss then somewhere along the line they pulled support for it. So I’ll try out the android app created by the author of ttrss, but the comments are… well.. interesting?