It seems to be nearly instant on the update so there has to be some
direct hook to SVN. Nice.
On 05/24/2017 08:15 PM, Kevin A. McGrail wrote:
Yes the website uses something called svnpubsub and it rebuilds from an
svn commit.
Regards,
KAM
On May 24, 2017 9:11:25 PM EDT, Dave Jones <da...@apache.org> wrote:
Did the update to SVN, committed it and the
spamassassin.apache.org/update <http://spamassassin.apache.org/update>
automatically updated so there must be a
cron job there pulling frequently. Cool. I havesa-update.ena.com
<http://sa-update.ena.com> in
the list now with a low weight and I am seeing hits in my Apache logs on
both of thesa-update.ena.com <http://sa-update.ena.com> servers.
Dave
On 05/24/2017 07:42 PM, Dave Jones wrote:
Got it. I will setup the /updates directory to be managed by SVN
with
exclusions for all of the extra files.
The link I was missing that I understand now is the
spamassassin.apache.org/updates
<http://spamassassin.apache.org/updates> is managed from SVN.
Makes complete
sense now.
Dave
On 05/24/2017 07:36 PM, Kevin A. McGrail wrote:
I think there is a leap missing, sorry.
Ok, so mirrored.by <http://mirrored.by> is in svn in site/.
The copy for rsync should
perhaps be a checkout with the extra files on top. Then an
svn up
keeps things in sync.
Mirrored.by <http://Mirrored.by> should be cleared.up how to
update.
On 5/22/2017 8:15 PM, Dave Jones wrote:
I understand the concept of the rest of the steps below but
how does
this link what is in SVN to what is actually hosted at
http://spamassassin.apache.org/updates/MIRRORED.BY? Maybe I am
missing something...
Am I overthinking this? I am not seeing the connection to
what is on
sa-vm1.apache.org <http://sa-vm1.apache.org>::updates and
spamassassin.apache.org/updates
<http://spamassassin.apache.org/updates>.
Regards,
KAM
