1. 36

  2. 12

    Miniflux has let me fall in like with RSS again. I’m running it via docker-compose on an Ubuntu VM with Portainer managing most of my network services. I’ve got it behind Traefik so I can access it at my equivalent of http://miniflux.home.lan.

    I’ve put fewer than a dozen feeds in it in the last ~2 months and I’m reserving it only for things I don’t ever want to miss a single post from but also if I lose my feed list, I would be able to recreate it relatively quickly.

    1. 4

      I second Miniflux, it’s refreshingly simple and fast.

      1. 3

        I payed for the hosted version of miniflux. It’s literally just $15/year, which is a steal, and there’s a 15 day free trial so you can really make up your mind. I never knew I needed RSS, until miniflux.

        1. 1

          I also am a happy Miniflux user.

          My setup is a free Heroku instance. I am running it for a few months now and don’t see any issues. The only drawback is that I have to manually refresh the feeds. Deployment takes no time, upgrade is automatic whenever my GitHub repository is updated.

          1. 1

            Miniflux seems awesome, but I see that it currently only uses Fever API which is quite limited and FreshRSS/Google Reader API is still on the “requested” side :(

          2. 8

            I’ve gone the entirely opposite way (opposite to the author’s “Newsletter” section, at least) and have set up rss2email for the feeds I follow – setup was a breeze, adding new feeds is simple, and one could probably run this as a cron/systemd timer, if running on a server isn’t an option.

            Almost any platform I’ve used has an email client available that is at least bearable for long-form reading, you can read offline, you can use filters to automatically file new items, and so on. I’m sure clutter is a consideration, but subscribing to any mailing list is probably far worse so. Nevertheless, I subscribe to more low-volume feeds, and so haven’t had to make any adjustments to my mail setup.

            Good writeup either way!

            1. 1

              I’m also having rss feeds sent to my inbox, using https://github.com/fgeller/feeder and a daily cronjob. Feeds go into a yaml file and that’s about it.

            2. 4

              Darn, I really wish this supported SQLite. Having gone down the self-hosted route for many applications in the past, I no longer have the tolerance or interest in maintaining a Postgres database for anything I self-host.

              1. 3

                I second this. This is for me the second biggest obstacle to self host webapps after “requires PHP”.

                1. 3

                  PHP is a complete non-starter for me. If I want it bad enough (and don’t have an alternative), I’ll set up Postgres.

                  In this case, the hosted offering (15-day trial, $15/year) is reasonable enough that I might just pay for that.

                2. 3

                  My miniflux postgresql was setup once then forget. Create a user, dB, install and setup backups. Why do you resent it?

                  1. 2

                    It’s the updates generally. Postgres major version upgrades are a pain. In my experience, the latency of version available on my distro was enough to significantly cut into the support lifecycle of the release to the point where I needed to upgrade. On top of that, user management is sort of a pain if multiple applications are using the same instance.

                    1. 1

                      I just use the official containers for these reasons.

                3. 3

                  I have been working on a fork of feedbin, which, IMO, is the best web-based RSS reader, for easier self-hosting. It’s in a really early stage right now, but in the meantime, it was fairly easy to create a docker image and deploy the official source to a server (though it required an increase in swap to run properly). I have tried other feed readers in the past but none of them really caught my attention as much as feedbin did. It even works just fine as a PWA!

                  1. 4

                    why fork it instead of contribute back to it? what additional stuff does your fork offer?

                    1. 3

                      Well I’m making some changes that wouldn’t really work for production use, such as limiting to one user (with the ability to invite others) and using SQLite instead of PostgreSQL.

                      1. 2

                        Those changes sound great, I hope you make your fork available for others!

                        1. 2

                          I will! For now only the single user functionality has been implemented (no invites yet) but you can check it out at https://github.com/pta2002/feedbiny

                  2. 2

                    Does anyone I am new to RSS, and I am astounded at how unadulterated it is compared to modern websites. I usually browse solar/renewable energy feeds and, shamefully, been using feedly. So, I’ll look into Miniflux, thanks for sharing this.

                    Does anyone know of an RSS reader that you can use to amalgamate articles and create a new RSS feed?

                    1. 2

                      You might want to look into the notion of a planet.

                      1. 1

                        Ah, this may fit my needs quite well.

                        Argh.. the repo looks like it is no longer available on gnome.org, fortunately, it looks like there are a number repos on github. Thanks for sharing this with me.

                    2. 1

                      Regarding the section to update RSS-Bridge: There’s also docker-compose pull. And then just run docker-compose up -d and it runs the latest version.