Hi all. I recently ported the Tiny Tiny RSS server backend from PHP to Rust, with the help of a self-hosted AI: https://github.com/slydetector/ttrss-rust If you already run tt-rss, this is a drop-in replacement for the server, not a new reader: The web UI is the original, untouched frontend Your Postgres database is unchanged. There's an importdb command that pulls your existing tt-rss database into the new instance, so it's a like-for-like swap All first-party PHP plugins are ported to Rust, and the tt-rss JSON API is the same, so clients that speak the tt-rss protocol (the official tt-rss mobile apps, Fiery Feeds, Tiny Reader) keep working as-is The usual 4-container PHP stack (app + updater + nginx + db) shrinks to two containers (rust app + db) Why? This started as an experiment: can a fully self-hosted LLM on consumer-grade hardware port a large, complex PHP codebase to Rust? The answer is a resounding yes. It's now my daily driver, and I plan to keep it in sync with upstream PHP. Honest caveats: 3rd-party PHP plugins are incompatible (they'd need porting) I don't use the CLI, so I didn't port it Configuration via PHP obviously doesn't apply; env vars work out of the box Feedback welcome, especially from tt-rss users who want to try swapping backends.   submitted by   /u/redit_ttrss   to   r/rss [link]   [comments]