[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
Tiny Tiny RSS • Periodic releases are over - Page 3
Page 3 of 7

Re: Periodic releases are over

Posted: 02 Feb 2015, 06:46
by sleeper_service

Re: Periodic releases are over

Posted: 02 Feb 2015, 07:18
by unlogy

Re: Periodic releases are over

Posted: 02 Feb 2015, 07:38
by HunterZ

Re: Periodic releases are over

Posted: 02 Feb 2015, 20:51
by Louie

Re: Periodic releases are over

Posted: 02 Feb 2015, 21:00
by fox
it's not in the repository so nothing.

Re: Periodic releases are over

Posted: 02 Feb 2015, 22:07
by HunterZ
Louie: config.php is actually in .gitignore - along with a bunch of other stuff - so git won't even look at it.

Re: Periodic releases are over

Posted: 03 Feb 2015, 14:40
by fox
I've added a placeholder update checker thing which would show the icon on the main UI if there are new changesets.

Re: Periodic releases are over

Posted: 03 Feb 2015, 20:59
by gbcox
@Louie,
I created a stand alone utility (cfg_ttrss) which can be used to sync config changes. It was mentioned in the forum
a while back and you can read about it here:


It was originally intended for those who weren't running the git version, but can be used for those who decide not to
use the full git_ttrss which I discussed earlier.

What I found was that every once in awhile a change would occur to the config file, and unless you were paying attention
and manually checking it every time you did an update, you'd miss the changes. Depending on what it was, it could
cause an issue.

If you are using the git_ttrss utility you don't have to worry about it. It automatically checks for any config file changes,
among other things, each time it runs.

Re: Periodic releases are over

Posted: 03 Feb 2015, 21:32
by gbcox
For anyone who's interested... here is the output from my run this morning. It shows cfg-o-matic at work...


Re: Periodic releases are over

Posted: 03 Feb 2015, 23:13
by cktt

Re: Periodic releases are over

Posted: 04 Feb 2015, 00:01
by cktt
Oops!

I figured out that there are files in my tt-rss/lock folder, I deleted them and it's working now
Sorry, stupid me

Re: Periodic releases are over

Posted: 04 Feb 2015, 23:17
by scottjl

Re: Periodic releases are over

Posted: 05 Feb 2015, 22:30
by cktt
Nice tweaks scottjl, thanks!

Re: Periodic releases are over

Posted: 06 Feb 2015, 19:26
by dswd
Hi, I have been using tt-rss for quite some time now. I am self-hosting a lot of software and try to keep my server updated to avoid security issues.
I don't mind using git, I use it on my own projects a lot. However I currently don't see a way to keep my server updated in a secure way using only git.
I don't want to automatically update via git because that gives me no way to review code changes. This option essentially gives anyone with commit permissions full control over my server. I also don't have enough time to watch github commits to see if there is some security fix burried in the commit logs.
If you want to abandon tarball releases and move to git fine, but please establish a way to inform users of security problems. I recommend using an rss feed for that. ;-)

Re: Periodic releases are over

Posted: 06 Feb 2015, 20:10
by fox
hello, dswd. welcome to our forums. this may come as a surprise but you are really fucking dumb. sorry.

let's go through your dumb post:

1. an SCM where you can see per-changeset diffs somehow gives you no way to "review code changes" but downloading a huge-ass tarball once a few months with god knows how many changes instead does. this is profoundly retarded thing to say in itself, i mean it's just so fucking dumb it makes my head hurt.

i'm sure before updating the tarball-updater way you made a unified diff of tt-rss-old and tt-rss-new and went through it by hand, you luddite. that is, while actually being capable of understanding the actual changes and their underlying reasoning. otherwise you're just shitting me with all this crap about security issues you allegedly care so much about.

1A. as a sidenote, i have significant doubts that you have the capacity of reviewing shit. lol.
1B. i'm not going to get into the apparent false dichotomy of an SCM forcing you to do unattended upgrades for some reason because, well, why bother.

2. anyway, if you read the op before posting retarded shit itt, you'd know that "releases" in tt-rss sense had always been nothing more than trunk snapshots made when i sorta-kinda felt like it. i.e. the exact same fucking code committed by people with exact same commit rights (that is, me) only delivered to you at random intervals and in a highly inefficient way.

which brings us to 3:

3. so, i guess what i'm saying is, instead of trying to ;) recommend me anything ;), you should stop and rethink your life of apparent ignorance and inability to reason which led you to the point whereas you made the above post in this here thread, forumposter dswd.

but wait, there's more:

4. fortunately, luckily for you, despite the absolute idiocy wrt anything related to securing your personal data, i can absolutely guarantee you that nobody in the world fucking cares about your rss feeds, so you are absolutely safe. so there's that at least. you can revel in joy being saved by your own insignificance.

i'm not sure why so many of your ~i'm gonna host my own shit for privacy and owning big corporations~ types are so hilariously dumb but lol if you think you're the first one and sadly i know you're not the last one.