You can. I do. Synchronization of read status between devices is a matter of taste. Without it it's as easy as running a native RSS reader (and it doesn't even have to be the same one!) on each computer. It's easy with opml export to keep the subscriptions the same when you do add or remove on a device.
>Put it in a docker or qemu
I'm trying to avoid inserting extra abstraction layers (browserOS on top of OS) in the first place. Adding more just to contain the needless complexity of the separate webserver+database isn't my jam.
I guess your RSS reading habits are quite different from those of me and other people that are the target audience for these kinds of self-hosted solutions. Not having read status synced across my devices is not an option, I might just as well use only one device in that case.
That's right. The computer is there to automate things for us, and having to deal with the same, already read articles manually on multiple devices is inconvenient.
What's really inconvienient is having to run an extra webserver and database 24/7 and keeping it all secure and up to date. Seeing a RSS entry twice is barely noticible.
Simply read RSS/Atom via mail (Rss2Email, for instance, there are few others) and simply have your mail synchronized as usual via IMAP. No need of a LAMP stack.
>Put it in a docker or qemu
I'm trying to avoid inserting extra abstraction layers (browserOS on top of OS) in the first place. Adding more just to contain the needless complexity of the separate webserver+database isn't my jam.