Periodic releases are over

[fox]

TLDR: tt-rss now uses rolling release model based on git master branch. There will be no more numbered releases, use git instead.

I'm not really seeing any point in continuing to make arbitrary trunk snapshots aka "releases" once every few months, so I suggest everyone switch to Git already. This way you don't stay with broken af_comics or whatever other plugin for literal months if some stupid site suddenly changes its
layout.

e: Not sure about this yet: I'm going to deprecate and remove .zip updating components and from now on assume that everyone is on Git. If that's too hard for you, download .tar.gz snapshots yourself on Github.

e2: in case this wasn't obvious the development will continue as usual it's just that there won't be any new tarballs

[blainemono]

This is a slap in the face for all loyal users, I for one won't stand idly while a travesty like this happens.

I'll rather sit.

[Aldursil]

Does this mean the updating from within TT-RSS will not work anymore?

I assume it does but wanted to be sure.

[tagno25]

Would you be willing to make the update function inside TT-RSS to check for new git updates, and be able to do a git pull?

[JustAMacUser]

Git is really easy. To install

Code: Select all

git clone https://github.com/gothfox/Tiny-Tiny-RSS tt-rss

To update:

Code: Select all

git pull

Depending on your setup you may need to update the permissions, etc. But otherwise it's really that easy.

[trammel]

I'm not really seeing any point in continuing to make arbitrary trunk snapshots aka "releases" once every few months, so I suggest everyone switch to Git already. This way you don't stay with broken af_comics or whatever other plugin for literal months if some stupid site suddenly changes its layout.

e: Not sure about this yet: I'm going to deprecate and remove .zip updating components and from now on assume that everyone is on Git. If that's too hard for you, download .tar.gz snapshots yourself on Github.

I've been running off git master for a year or more, with a daily cron job to backup the database, then do a git-pull.

Zero issues, never had to restore the database. It's a very stable codebase.

[fox]

Like I said, I'm not removing the tag-based tarball updater yet, but I don't plan on tagging any new releases in the foreseeable future so it won't do anything.

Maybe the compromise solution would be automatically tagging every week so that it would still work.

[reibuehl]

What is the best way to switch from the updater module to git based updating? Is it sufficient to rename the old directory, do the git pull and then copy the old config.php into the new directory? Or are there other steps needed?

[HeikoAdams]

Sounds like rolling release modell.

If I'm right, maybe you should think about switching version-number-scheme to something like yyyymmdd.

[fox]

ye this makes sense

[fox]

What is the best way to switch from the updater module to git based updating? Is it sufficient to rename the old directory, do the git pull and then copy the old config.php into the new directory? Or are there other steps needed?

not really but don't forget about custom plugins or themes if you got any

then its just git pull from then on

[Louie]

What is the best way to switch from the updater module to git based updating? Is it sufficient to rename the old directory, do the git pull and then copy the old config.php into the new directory? Or are there other steps needed?

not really but don't forget about custom plugins or themes if you got any

then its just git pull from then on

Fox do you have a recommended frequency on doing a git pull? daily/weekly/monthly? Also, should access to the tt-rss server be restricted when updating the code?

[fox]

idk do it when you feel like it, it's rarely broken

>Also, should access to the tt-rss server be restricted when updating the code?

I wouldn't really bother with that either.

[xtaz]

I've been pulling the latest git updates pretty much daily or so for a couple of years now. It's hugely easier to do than playing around with tarball releases. Things like the af_comics filters get fixed in a day or so instead of having to wait for months. The only time really I've ever had to do more work is when fox updated a lot of the fonts and font sizes in CSS which meant that I had to go and update my user CSS for the new changes. But using git it's actually easier than it would be from tarball cuz I can use things like git log and git show to see exactly what's been changed rather than having to guess.

I switched to a similar model with a lot of other stuff I have installed even though their master branches are not stable. Instead just checking out the specific release branch or tag and then changing the branch/tag when a new release comes out. Even doing that is easier than tarballs.

[gbcox]

I created a series of scripts which automatically do quite a bit of things such as:

Apply git updates
Check for and handle config file changes
Check for schema changes
Do database backups and rotation

It's easy to setup, just clone it from the bitbucket git repo and follow the instructions. I've been using it for almost 2 years.

You can read about it here: http://tso.bzb.us/2013/06/ttrss-utils-fedora-tiny-tiny-rss.html
There is also an earlier forum post on it.