49
After getting burned by Pocket, I moved everything into a self-hosted setup.
Current stack:
- FreshRSS for feed ingestion
- Readeck for actual reading
- Linkwarden for long-term storage
Running on Docker Swarm behind Traefik, internal-only. Remote access via WireGuard.
A few gotchas that took longer than expected:
- Readeck container entrypoint pointing at /readeck (dir) instead of /bin/readeck
- Linkwarden auth issues due to build-time NEXT_PUBLIC_* vars
- Had to seed the first user manually in Postgres with bcrypt
- Internal SMTP relay quirks between services
It’s definitely more work than SaaS, but the upside is ownership.
Full write-up with configs + fixes: https://clifmo.com/blog/posts/saas-is-temporary-your-reading-list-doesnt-have-to-be
Curious what others are using for this now. I considered Wallabag but opted for Readeck, even tho the Readeck Android app has a crash loop right now (for me).
Genuine question: why not just read on FreshRSS? What am I missing?
Not every site makes RSS available. Edit: and generally, I have so many RSS feeds, I'm scanning and looking for interesting things. At that point, I rarely have time to sit and read a long-form article. Rather than favorite it, mark it as unread or try to find it later, I send it to Readeck for when I'm ready to focus.
Not the OP but:
FreshRSS interface is kind of ugly (probably can be tweaked). You can use third party RSS readers, but that ends up being almost as much work as installing readeck and the like.
FreshRSS doesn't support OPDS or have any koreader integration, unlike readeck. These are essential features for reading on an e-ink reader, which is my preferred way to read longer articles in particular.