Tiny-Tiny-RSS VS Portainer

I just want to vent here a bit:

Feedly is the only app I ditched because I did not understand the interface. AT ALL. I tried multiple times, like really hard, over the course of 2-3 years, and all it delivered was a feeling of being insanely stupid.

I started my attempts around 2012 (kind of around Google killing Reader). I could not understand if that app even deliver that same functionality as Reader, could not understand if it allows to just add custom RSS url. I was not sure which title-description was an actual pair. I struggled to find article boundaries - I scrolled while reading and it suddenly just closed that and opened another unrelated thing. I struggled to use categories. I struggled to stabilize the layout - every week or so it switched from a list, to two-pane thumbnails, then some other weird view. I tried to set up my custom view but it just toyed with me. It took me an embarrassing amount of time to figure out how to actually browse my feeds by publish time (instead of some random metric app thrown them at me).

Dark theme just made it even harder - I had no idea what I'm looking at. I felt that I have more control over watching commercials on TV, than actually using Feedly.

It made me start hosting TinyTinyRSS [0] app on public internet for me and friends for many years. When I finally turned off tt-rss instance (due to my servers going down permanently) I came back to feedly... to just realize I don't even try to use it any more. A decade old frustration ended up with simply uninstalling.

[0] https://tt-rss.org/

> I want to host my own RSS server though and then maybe use a native reader to view it, like an RSS of RSS feeds.

I've been using Tiny Tiny RSS to do this for years. It works very well. https://tt-rss.org/

Tiny Tiny RSS (TT-RSS) https://tt-rss.org/ is a self-hosted, open-source RSS feed reader that provides a lightweight and customizable solution for managing and reading RSS feeds. It offers a simple web-based interface, allowing users to aggregate, organize, and access their favorite content from various sources in one centralized location. With its extensibility and robust feature set, TT-RSS offers a powerful tool for individuals who prefer to have full control over their RSS reading experience. As a dedicated programmer and avid user of Tiny Tiny RSS (TT-RSS), I can confidently say that it is an exceptional self-hosted, open-source RSS feed reader. With TT-RSS, I have the freedom to personalize and fine-tune my RSS reading experience to perfection. Its lightweight web-based interface offers a seamless way to aggregate, organize, and access all my favorite content from a multitude of sources. TT-RSS has become an indispensable tool in my daily routine, empowering me to stay informed, discover new insights, and effortlessly manage my RSS feeds with ease. If you're a fellow developer seeking a powerful, customizable RSS reader, TT-RSS is an absolute game-changer.

I would recommend Tiny Tiny RSS or FreshRSS as examples but you can use anything you want, there's plenty of them. Why would you want to pay for something like this?

Tiny Tiny RSS

Back when I was using Tiny Tiny RSS I've developed af_feedmod to download the article from the linked webpage so you'd end up with a full feed. This was later forked into FeedIron and seems to be somewhat popular by now.

TinyTinyRSS feed aggregator

Have you seen https://tt-rss.org/

Portainer

> Any tips on the minimum hardware or VPS's needed to get a small swarm cluster setup?

From my testing, Docker Swarm is very lightweight, uses less memory than both Hashicorp Nomad and lightweight Kubernetes distros (like K3s). Most of the resource requirements will depend on what containers you actually want to run on the nodes.

You might build a cluster from a bunch of Raspberry Pis, some old OptiPlex boxes or laptops, or whatever you have laying around and it's mostly going to be okay. On a practical level, anything with 1-2 CPU cores and 4 GB of RAM will be okay for running any actually useful software, like a web server/reverse proxy, some databases (PostgreSQL/MySQL/MariaDB), as well as either something for a back end or some pre-packaged software, like Nextcloud.

So, even 5$/month VPSes are more than suitable, even from some of the more cheap hosts like Hetzner or Contabo (though the latter has a bad rep for limited/no support).

That said, you might also want to look at something like Portainer for a nice web based UI, for administering the cluster more easily, it really helps with discoverability and also gives you redeploy web hooks, to make CI easier: https://www.portainer.io/ (works for both Docker Swarm as well as Kubernetes, except the Kubernetes ingress control was a little bit clunky with Traefik instead of Nginx)

In this section, we will add Portainer to help us in managing our Docker containers. You can find more details about it here. To integrate Portainer into our EC2 project, we can follow these steps:

Git issues pointing to: https://docs.portainer.io/v/ce-2.9/start/install/agent/swarm/linux gives a ERR_TOO_MANY_REDIRECTS.

I am currently running Portainer, but webhooks (GitOps) appear to be broken ( [2.19.0] GitOps Updates not automatically polling from git · Issue #10309 · portainer/portainer · GitHub ) and so I cannot send webhook to redeploy a stack. So, looking for alternatives. Using this as a good excuse to learn more about docker and CI/CD etc.

A Synology NAS running Portainer (https://www.portainer.io/) running Paperless NGX (https://github.com/paperless-ngx/paperless-ngx)

This works better than I can possibly tell you.

I have an Epson WorkForce ES-580W that I bought when my mother passed away to bulk scan documents and it scans everything, double-sided if required, multi-page PDFs if required, at very high speed and uploads everything to OneDrive, at which point I drag and drop everything into Paperless.

I could, thinking about it, have the scanner email stuff to Paperless. Might investigate that today.

Paperless will OCR it and make it all searchable. This setup is amazing, I love living in the future.

> I've come to the conclusion (after trying kops, kubespray, kubeadm, kubeone, GKE, EKS) that if you're looking for < 100 node cluster, docker swarm should suffice. Easier to setup, maintain and upgrade.

Personally, I'd also consider throwing Portainer in there, which gives you both a nice way to interact with the cluster, as well as things like webhooks: https://www.portainer.io/

With something like Apache, Nginx, Caddy or something else acting as your "ingress" (taking care of TLS, reverse proxy, headers, rate limits, sometimes mTLS etc.) it's a surprisingly simple setup, at least for simple architectures.

casaos it just makes things like backups, offsite syncing and many other nas related things so much easier to manage. And gives you a proper nas like experience similar to that in which you'd fine on companies like tnas or synology. I actually also use it as a replacement for portainer when i don't need the more advanced features it offers

> I moved to docker swarm and love it. It's so much easier, straight forward, automatic ingress network and failover were all working out of the box. I'll stay with swarm for now.

I've had decent luck in the past with the K3s distribution, which is a bit cut down Kubernetes: https://k3s.io/

It also integrates nicely with Portainer (aside from occasional Traefik ingress weirdness sometimes), which I already use for Swarm and would suggest to anyone that wants a nice web based UI: https://www.portainer.io/

Others might also mention K0s, MicroK8s or others - there's lots of options there. But even so, I still run Docker Swarm for most of my private stuff as well and it's a breeze.

For my needs, it has just the right amount of abstractions: stacks with services that use networks and can have some storage in the form of volumes or bind mounts. Configuration in the form of environment variables and/or mounted files (or secrets), some deployment constraints and dependencies sometimes, some health checks and restart policies, as well as resource limits.

If I need a mail server, then I just have a container that binds to the ports (even low port numbers) that I need and configure it. If I need a web server, then I can just run Apache/Nginx/Caddy and use more or less 1:1 configuration files that I'd use when setting up either outside of containers, but with the added benefit of being able to refer to other apps by their service names (or aliases, if they have underscores in the names, which sometimes isn't liked).

At a certain scale, it's dead simple to use - no need for PVs and PVCs, no need for Ingress and Service abstractions, or lots and lots of templating that Helm charts would have (although those are nice in other ways).