Reading & News Stack

Last reviewed Oct 11, 2026 · 662 words

Give each app one job and one direction of flow: Miniflux is where things arrive, Wallabag is where you send what you mean to read, and Linkwarden is where you keep what you want forever. Miniflux has built-in integrations for both, so a single keypress moves an article down the line. The three need about 1,664 MB of RAM by the directory's estimates: 128 MB for Miniflux, 512 MB for Wallabag and 1,024 MB for Linkwarden, which spends it on archiving full pages.

What talks to what

Miniflux fetches your feeds and shows them in a fast, keyboard-driven list. In its integration settings you can connect it to Wallabag and to Linkwarden with their API credentials; after that, saving an entry pushes it to whichever service you enabled. Its compatible APIs also let third-party mobile readers connect.

Wallabag extracts the readable text of each article, stores it, and serves it to its mobile apps and browser extensions for offline reading. It exports to ePub and PDF, which is handy for e-readers.

Linkwarden saves a link along with a full archived copy of the page, organised into collections with tags and full-text search. It is the only one of the three designed to survive the original page disappearing.

Can Miniflux and Linkwarden share one Postgres?

Yes. Both require PostgreSQL, and Miniflux has no SQLite fallback at all, so running one Postgres container with a separate database and user for each app saves memory and gives you one thing to back up instead of two. Keep the credentials separate so neither app can read the other's data. The trade-off is a shared upgrade path: when you move to a new Postgres major version, both apps go down together, so plan that as one maintenance window. Wallabag can point at the same server too if you configure it for Postgres.

Deploy in this order

Database first, then Miniflux, because it is the source of everything else. The catalogue's compose file shows the pattern: a DATABASE_URL, RUN_MIGRATIONS=1, and an admin account created on first start. Import your OPML and live with it for a few days.

Wallabag second, then connect it from Miniflux's integration page and test with one article. Linkwarden last; connect it the same way, and install its browser extension for pages you find outside your feeds. Put all three behind your reverse proxy on their own subdomains. Wallabag in particular builds its links from the domain it is configured with, so set that to the public URL before you save anything.

The mistake: saving everything everywhere

With integrations configured, it is tempting to send every interesting article to both Wallabag and Linkwarden. Within a month you have two piles of the same links, neither of which you trust as the complete record. Decide the rule up front: Wallabag is a queue you empty, Linkwarden is an archive you add to rarely and deliberately. Linkwarden's archiving uses more storage than plain bookmarks, so a habit of archiving every link also shows up on your disk.

Backups

Dump the shared Postgres nightly, which covers Miniflux and Linkwarden metadata. Linkwarden's archived page files live on disk outside the database, so back up its data volume too. Back up Wallabag's database and its data volume.

What I'd do

Start with Miniflux alone for a week, add Wallabag once you notice you are leaving tabs open, and add Linkwarden only when you lose a page you wanted to keep. If Miniflux feels too spare, the FreshRSS vs Miniflux comparison covers the friendlier option, and RSS isn't dead makes the case for the whole habit.