{"id":1726,"date":"2020-05-13T21:24:34","date_gmt":"2020-05-14T01:24:34","guid":{"rendered":"https:\/\/lowtek.ca\/roo\/?p=1726"},"modified":"2020-05-13T21:24:34","modified_gmt":"2020-05-14T01:24:34","slug":"hello-freshrss","status":"publish","type":"post","link":"https:\/\/lowtek.ca\/roo\/2020\/hello-freshrss\/","title":{"rendered":"Hello FreshRSS"},"content":{"rendered":"

\"\"<\/p>\n

Well, it was time for a new RSS feed reader – and FreshRSS<\/a> was the best choice for me. The kind folk at linuxserver.io<\/a> maintain a container<\/a> for it, and it fits nicely into my nginx<\/a> setup.<\/p>\n

Moving to a new tool for anything will have an adjustment period, it would be nice if the user experience was identical – but there is also something to be said about trying new things. Different isn’t always bad, change can be for the better.<\/p>\n

Setting it up on a basic linux install<\/a> looks simple, but I would suggest that adopting a container version is even easier. FreshRSS bootstraps and has a guided setup for first run (first connect on the web). You can even pick a sqlite database<\/a> and avoid any database setup. It supports OPML<\/a> import, which many other RSS feed readers support as well – so getting your feeds in or out of FreshRSS is easy.<\/p>\n

My initial kick the tires install, I use the no-database required sqlite configuration. This worked well, but as I already run MySQL for my wordpress installs<\/a>, why not use the same data store?<\/p>\n

This is very easy – and the MySQL is also running in a container. The linux install covers how to setup your database, but as I’m using a container version I need to make one change to the setup – because ‘localhost’ isn’t the source of the network traffic to the container. (this is the use of ‘%’ instead of ‘localhost’ as shown below)<\/p>\n

mysql> CREATE USER 'freshrss'@'%' IDENTIFIED BY 'SECRET-PASSWORD-PHRASE';\r\nQuery OK, 0 rows affected (0.01 sec)\r\n\r\nmysql> CREATE DATABASE `freshrss`;\r\nQuery OK, 1 row affected (0.00 sec)\r\n\r\nmysql> GRANT ALL privileges ON `freshrss`.* TO 'freshrss'@'%';\r\nQuery OK, 0 rows affected (0.00 sec)\r\n\r\nmysql> FLUSH PRIVILEGES;\r\nQuery OK, 0 rows affected (0.00 sec)<\/pre>\n
While allowing access from any host is a bit security scary, the container is already isolated to a private network so I’ve got layers of protection already.<\/p>\n
During the web first run setup you have to then configure the database appropriately.<\/p>\n
\"\"<\/p>\n
That’s probably the most complicated part of the setup. Now it’s just a matter of creating a user, and importing the OPML of my feeds and away I go.<\/p>\n
Of course the new FreshRSS is going to ‘discover’ loads of new unread articles I’ve already read – and also for feeds I’ve been ignoring, not load enough unread articles. Oh well. So for a short while I run both – marking large chunks of articles as read in the new system, and burning down ones that were missed by the new system in the old one. It’s a one time hit and it gives me a chance to tweak some of the user setup configuration.<\/p>\n
I’m only a day or so into using FreshRSS – but I’m adapting quickly to the differences. I will shout out to the Android app FeedMe<\/a> which supports FreshRSS very nicely, once you enable the mobile API<\/a>.<\/p>\n
I will say that the themes are quite nice, I’m still getting use to the layout differences between it and the previous reader I was using. No regrets in making the switch to FreshRSS.<\/p>\n","protected":false},"excerpt":{"rendered":"
Well, it was time for a new RSS feed reader – and FreshRSS was the best choice for me. The kind folk at linuxserver.io maintain a container for it, and it fits nicely into my nginx setup. Moving to a new tool for anything will have an adjustment period, it would be nice if the … Continue reading “Hello FreshRSS”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-1726","post","type-post","status-publish","format-standard","hentry","category-computing"],"_links":{"self":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/1726","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/comments?post=1726"}],"version-history":[{"count":2,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/1726\/revisions"}],"predecessor-version":[{"id":1730,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/1726\/revisions\/1730"}],"wp:attachment":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/media?parent=1726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/categories?post=1726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/tags?post=1726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}