Switch to regular (automatic?) update scheme for rolling release apps
-
For tiny tiny RSS, as for other apps with a rolling release model, it would make sense to switch to a regular or automatic update scheme. Is that feasible?
In the specific case of tiny tiny RSS, updates rarely to never break anything and/or introduce new database schemes.
-
@necrevistonnezr Are you requesting that the app be able to update itself? On a side note, we did push a ttrss update yesterday.
-
I don't know what's the best way - is it feasible that the user could pull the newest git release? Or maybe just do an automatic git pull on your side and push an update once a week?
-
Please update - a lot of commits in the last weeks...
-
There will be no more periodic tags for TT-RSS. Git Master is the only supported version. Maybe it's time again to think about a rolling release for this app? And switch to PostgreSQL as recommended by the Author while you're at it?
https://community.tt-rss.org/t/versioning-changes-for-trunk/2974/
I’m tired of people (this means package and container maintainers, not end-users) who stay on tt-rss tags instead of git master for whatever reason.
Therefore,- Don’t expect any more periodic tags, ever. Prepare to stay in August 2019 forever if you’re using that particularly terrible “linuxserver” container.
- Static version prefix is no longer going to be a thing. Your either run off git and get correct timestamp and commit you’re on (because this information is actually useful to help you in case something is broken), or you get “Unknown (unsupported)” because, as far as I’m concerned, that’s what you’re running.
- As before, only latest code off git master is supported. If you’re running anything else, update before reporting any issues.
-
BTW: There are now official docker-compose scripts: https://git.tt-rss.org/fox/ttrss-docker-compose
