Seeking New Maintainers for This Repository

[HenryQW]

Dear fellow RSS enthusiasts,

Unfortunately, due to personal circumstances (busy work, auh.), I am unable to commit enough time to maintain this repository to a satisfactory standard.

Background of This Repo

The original motivation behind creating this repository was to simplify the deployment process for TTRSS, which did not support Docker deployment back in 2017. I forked this repo from @rubenv https://github.com/rubenv/docker-ttrss to offer a more user-friendly solution. I then bundled plugins I deemed useful, I hope you find them useful too ⭐️.

Since then, TTRSS has gradually added Docker support through docker-compose.yml, which in my opinion, might not be the best approach for updating a containerized application, but it works in a much more stable way.

This repo, as it simply wraps TTRSS upstream and containerizes the codebase, always suffers from instability issues, e.g, breaking changes, dependency compatibility. Thus requires effort to maintain it, which is something I am no longer able to provide due to personal circumstances (I've relocated to 3 countries since 2017, wow! )

Some Stats

Over the past 6 years:

Over 8.1M docker pulls

Over 130K visits to the doc site

As the saying goes, you either grow with your users or grow old with them. In this case, I find myself growing old with all of you ❤️.

To date, I still find RSS to be the best way to acquire information from this increasingly fragmented, closed-off, algorithmically polluted internet. I spend at least an hour reading my RSS feed every day. That's why I hope this repository can continue to serve everyone for as long as it's able.

Maintainer Resposibility

Make sure the docker image continues to work:

1. Keep up with the upstream updates
2. Improve where necessary, but keep it stable
3. Bug fixes

If you are interested in taking up the task of maintaining this repository, I would be very grateful. Please leave a message here to express your interest.

Long live RSS!

[rubenv]

@HenryQW happy to have indirectly contributed to this all! 😅

[dimon222]

Perhaps worth to research if we can have best of two worlds - base off official docker image with any extra tweaks on top that are specific to Awesome TTRSS this way reducing maintenance burden to minimum? Up to "plugins only" perhaps.

[HenryQW]

Yes I agree this is a great approach.

[dimon222]

I suppose @TonyRL took over and this can be closed now? Kudos Tony for keeping this project going!
But nevertheless I still feel it might be more sustainable longer term to try approach I suggested above - try to base it on top of official image of Tiny Tiny RSS with only "Awesome" modules on top. Its very subjective opinion of course. But it might make things muuuch simpler to maintain. I have my own private fork on top of Full Text RSS (paid one, of course) instead of Mercury. Sadly I can't contribute my config because I see it will change the way too many things right now, but if this was more modular/smaller footprint of repository it might have got easier.

[TonyRL]

The official image setup is not a direct replacement for the current Awesome-TTRSS image. Additionally, requiring users to set up two additional containers does not really fit the "Dockerized all-in-one solution".

[dimon222]

I was in no way saying it is a replacement. I was suggesting it to use as "base" image (FROM statement in dockerfile) and add "awesomeness" on top. This will ensure closer compatibility, reduce maintenance burden.

[HenryQW]

I think it's a good approach. I remember that image was using git pull inside a running container to perform updates, so it might not work.