this post was submitted on 02 Apr 2026
33 points (94.6% liked)

Selfhosted

58093 readers
1093 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
33
Self-hosting a Pocket alternative using Readeck, Linkwarden, and Docker Swarm. (programming.dev)
submitted 14 hours ago by clifmo@programming.dev to c/selfhosted@lemmy.world
13 comments fedilink hide all child comments
 

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).

all 14 comments
sorted by: hot top controversial new old
[–] tuckerm@feddit.online 1 points 5 hours ago* (last edited 5 hours ago)

Thanks for writing that up! I'm curious: what makes you use Readeck for some things and Linkwarden for others? It seems like they have the same use case, and pretty much the same features.

I've been using wallabag for quite a while, before Linkwarden and Readeck were written, and I haven't felt a reason to switch away from it.

A thing I like doing with wallabag is:

  1. Select a bunch of articles that I want to read on my ebook reader
  2. Tag them as "exported_on_2026-04-02"
  3. Export them as an epub
  4. The epub is synced automatically by syncthing to my ebook reader (it's like an eink Android tablet)
  5. Once I've read that file on the ebook reader, select all entries tagged with "exported_on_2026-04-02" and mark them as read. Or just mark them as read right away, since I'll definitely get to them once they're on the ebook reader.

I haven't found any other bookmarking applications that can conveniently tag articles in bulk, export, and then mark as read in bulk like wallabag. From the website, it looks like Readeck can, I'll have to check it out.

[–] undrwater@lemmy.world 1 points 7 hours ago (1 children)

I self host wallabag for this. Unfortunately, I don't use it that much. I end up with a bunch of tabs.

[–] FarraigePlaisteach@lemmy.world 1 points 5 hours ago

I use it too. My main issue is that when I'm entering tag names on a new article, it doesn't suggest existing tags. Makes it very difficult to keep the number of tags limited. I might create #environment when #climate is what I would usually use.

[–] clifmo@programming.dev 6 points 12 hours ago

Go figure, my ISP went down and my self-hosted blog is temporarily unavailable. I have a backup internet connection and fail-over WAN, so I didn't even notice the blip thanks to pfsense.

But I need dynamic DNS or to use Cloudflare's load balancers or something. Anyone have experience with this?

[–] eodur@piefed.social 6 points 13 hours ago (1 children)

I use KaraKeep for this and couldn't be happier.

[–] med@sh.itjust.works 1 points 8 hours ago

Do you subscribe to karakeep lists? Are they of infinite length?

[–] irmadlad@lemmy.world 6 points 14 hours ago
  • Readeck for read it later articles
  • Linkwarden for important links
  • tt-rss for feed ingestion
[–] wilo108@lemmy.ml 3 points 13 hours ago (3 children)

Genuine question: why not just read on FreshRSS? What am I missing?

[–] vividspecter@aussie.zone 1 points 5 hours ago

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.

[–] clifmo@programming.dev 3 points 13 hours ago* (last edited 13 hours ago)

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.

[–] JensSpahnpasta@feddit.org 1 points 12 hours ago (2 children)

It's actually kind of crazy what amount of tech people have to use just to save a webpage for later reading.

[–] ragica@lemmy.ml 1 points 4 hours ago

But also it's kind of awesome.

[–] fluffy@feddit.org 2 points 9 hours ago

… just to save a webpage which they tell themselves they’ll read later (but probably won’t) …

I include myself in this