this post was submitted on 02 Apr 2026
41 points (95.6% liked)

Selfhosted

58148 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
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] JensSpahnpasta@feddit.org 1 points 18 hours ago (3 children)

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

[–] INeedMana@piefed.zip 1 points 57 minutes ago

have to use

Nah, Joplin/Logseq would probably be enough. It's the rest of the features where the slope gets slippery

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

But also it's kind of awesome.

[–] fluffy@feddit.org 3 points 15 hours ago

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

I include myself in this