Does it produce a rss feed itself?
Show HN: I built a tiny-VPS friendly RSS aggregator and reader
21–30 of 49 posts
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#22Cool project! Also it's welcome resource to learn, since I just started learning Go and was trying myself at an RSS reader (https://stille.app).
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#23This is what self-hosted software should be. An app, self-contained, (essentially) a single file with minimal dependencies. Not something so complex that it requires docker. Not something that requires you to install a separate database. Not something that depends on redis and other external services. I’ve turned down many self-hosted options due to the complexity of the setup and maintenance.
Agreed. Lately I'm coming across self-hosted services that not only require docker, they essentially require a docker-compose file full of many other dependencies.
The other thing that blows my mind is how many of these self-hosted applications require mysql/postgres instead of just using sqlite.
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#24Earlier quoted context omitted.
The docs literally specify it doesn't "Deploy with a single binary"
It would be nice if people realised that not everything is Linux (or Windows or Mac).
It explicitly states small VPS as a target, so - yes - Linux. I realize you can deploy non-Linux image on VPS, but hosting docker containers on Linux is the default
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#25Simple, no-fuss self-hosted server software should really be Rust, or Go / C++ if needed.
All three of them allow you embed the UI assets (media, JS, CSS) into the binary and all three work great with key/value stores (badger, leveldb, rocksdb, etc..) or SQLite.
There is no install. No setup. No packages to download first. Just a simple binary that respects OS signals, has crazy good throughput, and uses so little memory that your router can run it.
Please, consider moving your JVM/Node.js/Electron project to one of these as a chance to jump into really performant software.
(There are also a lot of RSS servers written in Rust/Go/C on Github: https://github.com/search?q=rss+host+language%3AGo+language%...)
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#26Simple, no-fuss self-hosted server software should really be Rust, or Go / C++ if needed. All three of them allow you embed the UI assets (media, JS, CSS) into the binary and all three work great with key/value stores (badger, leveldb, rocksdb, etc..) or SQLite. There is no install. No setup. No packages to download first. Just a simple binary that respects OS signals, has crazy good throughput, and uses so little me…
This one is written in Go. The front end in Svelte is built into static files and served by Go. The docker container just makes it easy to build but they do distribute a single static binary
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#27Earlier quoted context omitted.
Looks good! I am curious on why you recommend to deploy using docker, being a single binary with no external dependencies I find the deployment simple enough. I write all my personal projects using Go and one of the things I most like is that it compiles to a binary without external dependencies.
That's mostly for Windows users. The SQLite driver uses cgo, so we use both Ubuntu and Windows Server in CI to avoid cross-compiling. However, we still can't confirm that it's 100% ok on Windows. If any weird bugs occur on Windows, we don't have much experience or energy to deal with them. The Docker image is based on Debian, we are more familary with it.
For the SQLite driver, check out the one by modernc for pure Go
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#28Earlier quoted context omitted.
Almost guaranteed this doesn't build in ~2 years and you would likely need to know all of those languages to fix it.
Encountered the same problem last year. My tech stack was React Native as I was mostly building stuff that has few interactions and it was easy to get something good on both platforms. Then, I got a notice from Google about API version. Updating the project was such a nightmare due to compatibility issue. Some libraries were abandoned. Some had breaking changes. It was easier to write the two native versions than to…
For any project that you depend on that has opted into the NPM quagmire, you really should be running `git add --force ./node_modules` and periodically pushing a copy of this to a branch/repo that you control instead of depending on upstream, since most projects that ostensibly use Git tend to thwart its entire raison d'etre—hobbling its ability to do effective version control by abusing .gitignore for their overlay VCS of choice (i.e. the "package manager").
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#29Earlier quoted context omitted.
Encountered the same problem last year. My tech stack was React Native as I was mostly building stuff that has few interactions and it was easy to get something good on both platforms. Then, I got a notice from Google about API version. Updating the project was such a nightmare due to compatibility issue. Some libraries were abandoned. Some had breaking changes. It was easier to write the two native versions than to…
For any project that you depend on that has opted into the NPM quagmire, you really should be running `git add --force ./node_modules` and periodically pushing a copy of this to a branch/repo that you control instead of depending on upstream, since most projects that ostensibly use Git tend to thwart its entire raison d'etre—hobbling its ability to do effective version control by abusing .gitignore for their overlay…
The issue was not finding the libraries code. The issue was the churn. So one day, you have a (in my case, small) set of libraries to get things going. Then 2 years after, compilation issues as they all have different requirements. So you have to find another common intersection between them and the node/react-native versions. I should have vendored some in the project.
In Android, libraries are much stabler. Deprecated functions are picked by the IDE and an alternative is often presented in the comments. I'd much prefer to have big libraries (as we have tree-shaking) especially when dealing with frameworks instead of the bazillion packages when trying to do anything with npm.
Re: Show HN: I built a tiny-VPS friendly RSS aggregator and reader
#30You might have seen this already, but Rachel By The bay has a few recent blog posts on how feed readers commonly get things wrong, and a service she's got to "score" your feed reader based on it's observed behaviour:
https://rachelbythebay.com/w/2024/05/27/feed/
https://rachelbythebay.com/w/2024/05/29/score/
https://rachelbythebay.com/w/2024/05/30/fs/
Don't be "that guy" who releases software that once deployed widely creates "thundering herds" that knock unsuspecting websites down