ChrisFound the perfect combination for self-hosting my reading stack: Miniflux and Wallabag, you may now kiss!
Note: This is an update to “My reading stack”
Why?
Primarily for keeping the stuff I read private by self-hosting alternative services.
Additionally, to do all my reading from a web browser, without third party services and apps involved.
Another thing I wanted to experiment with was the interoperability between Miniflux and Wallabag.
How does it work?
Miniflux acts as my RSS feed reader, which integrates with the Wallabag API.
Wallabag is the alternative I use to Pocket, especially for longer reads.
In Miniflux I set up the integration to my Wallabag instance, so that when I hit “Save article”, it sends it to Wallabag so that I can read it later (if it’s a long read).
I access both services (under practical dns names) on my own domain (both from phone and PC).
Benefits
Both Miniflux and Wallabag can be “installed” as a PWA on your mobile device and accessed through a web browser on your PC.
No profiling, no tracking involved.
Extremely lightweight stack.
You use FOSS software, to which you can contribute to (or fork it).
Downsides
Minimum cost of 5$/month for hosting it on Linode or DigitalOcean.
You need to make sure your VPS is secured, duh.
So far I didn’t see any other downsides.
How to self-host
Both Miniflux and Wallabag have docker-compose files in their repositories, so the installation is quite trivial.
You’ll need to figure out the desired environment variables depending on your needs.
I host mine through caprover, through a Web UI it’s a few clicks away.
I plan on writing a detailed how to in the future.