Periodic releases are over

[IvanRaide]

I think this is going to hurt ... but, I'm confused by something.

I had the clone command done a while ago,

Code: Select all

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

and tried to update today using git pull. Doing the git pull it looked fine, but my version before the update was
v1.15.3.4ca621a but after the update its v1.15.3.dd6e238. Now I get this version number from preferences, but I noticed that in the wiki for filters https://tt-rss.org/redmine/projects/tt- ... entFilters it says 1.7.6 and so does roadmap at https://tt-rss.org/redmine/versions/88 . That said, the dd6e238 had an update a day ago https://github.com/gothfox/Tiny-Tiny-RS ... f14179112c , so am I just looking at the "wrong" version numbers? Is v1.15.3.dd6e238 the latest, and if yes, what is the 1.7.6 references for?

[fox]

idk maybe check the year there champ

[IvanRaide]

idk maybe check the year there champ

Wait a sec, its NOT 2013 ....

[masgo]

I an using ttrss on a hosted webspace. Because of that my rights as a user are quite limited, i.e., i can not install deamons. But I can run cron jobs. One drawback exists, because processes get killed by the system if they consume more than some hours of CPU time. So the updater gets killed every few days. To mitigate that I am running a script via cron (3x a day) to check if the updater is still running and restart it if not.

I also integrated the git pull command, so now my ttrss gets also updated every time is killed.

Here is the script, maybe it is of interest for some:

Code: Select all

#!/bin/bash

if [ `ps u | grep update.php | wc -l` != "2" ]; then
    git -C PATH_TO_TTRSS pull -q
    rm -f PATH_TO_TTRSS /nohup.out
    nohup /vrmd/webserver/php56/bin/php PATH_TO_TTRSS/update.php --daemon &
fi


before you ask: screen is not available.

[ylavi]

It's taken me a while to get round to it, but I've set up my installation for automatic updates using came88's script (https://tt-rss.org/forum/viewtopic.php?f=10&t=3262&start=60#p19511).

I'm unsure, though, how to have additional plugins (for example FeedIron) automatically update as well. I don't expect anyone to modify his script for me (but if you have one already that does the job, why not post it?). I'm just hoping for advice how to handle the various git repositories so I can fix up the process on my own, as I haven't done this before.

Do I put the plugin's repository inside $DIRGIT/plugins as an independent repository - in which case I would have to loop through all such directories to run git fetch/log/merge on each one - or will the git submodules function allow me to have the $DIRGIT repository handle the plugin repositories too and thereby make only minimal changes to the script? (i.e. run "git submodule update --remote" in $DIRGIT -- but I get the impression I still have to do that separately from updates to the main repo)

Tips/instructions will be very welcome! (fox, please go easy; and thanks for all your generous work)

Thanks

UPDATE:
I added one plugin as a submodule with "sudo git submodule add git://github.com/m42e/ttrss_plugin-feediron.git plugins/feediron" and added "git submodule foreach git fetch origin" and "git submodule foreach git merge origin/master" where appropriate in the script. My concern right now (and I don't see how to test that) is whether the command "git log HEAD..origin/master --oneline" will include changes to submodules too. I get the impression that it will, but can anyone confirm that?

[JonTheNiceGuy]

You may need to add other configuration changes in the sed section.

Sorted it out: https://gist.github.com/JonTheNiceGuy/2 ... e4d79549ce

I'm unsure, though, how to have additional plugins (for example FeedIron) automatically update as well.

This doesn't incorporate any checking of submodules, so if there's something I can do in my script to incorporate that, please comment on the gist!