I’ve been running it selfhosted since before the docker generation of tt-rss and I will keep running it as such also.
I hope the support for that will keep going or I will have to look for some other program that does the same.
VPS deployed via a simple jenkins job that rsync’s over the config, then docker-compose down/up…
I have it scheduled to run once a week just to get the automatic app/plugin upgrade on startup, but also have a branch of the git repo to add other services like caddy for automatic certificate renewal. I follow the docker-compose repo changes (via tt-rss of course) and rebase/deploy whenever there are changes. Could probably do something with cloning the original repo and adding a compose file override, but this works for me.
Run the backups manually every day as part of my general backup script, and have switched VPS providers a few times so run it manually then.
I’ve found the best way to jump in is to jump right in an start using it on-host to do simple things like add a new package and build up from there, doing a whole system transition directly to Ansible is a hell of a lot of work.
Home server bare metal Debian → docker-compose deployed via Ansible
I’m still running tt-rss on a shared hosting service. Pretty much the same as I already did two years ago. See my reply to the poll of Jun 25, 2021.
In my opinion, this is a very convenient way of running tt-rss with very less maintenance effort. Would be great if further development of tt-rss will keep this possibility.
I just got mine working yesterday using Docker compose on VPS. The tricky part was configuring nginx in front of it to do both ssl forwarding and ssl termination depending on the hostname so that some url’s get forwarded to my home network, and others ( list tt-rss ) to a web server running on the VPS.