W3C home > Mailing lists > Public > public-perma-id@w3.org > February 2016

Re: Problems and Opportunities at purl.org

From: David I. Lehn <dil@lehn.org>
Date: Mon, 29 Feb 2016 15:07:28 -0500
Message-ID: <CADcbRRMrD4i6FcWg4NyWDZLSCZw3Zoh6KKa9F-t6o397LrwW-w@mail.gmail.com>
To: Shane McCarron <shane@aptest.com>
Cc: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>, Pemanent Identifier CG <public-perma-id@w3.org>
On Mon, Feb 29, 2016 at 1:07 PM, Shane McCarron <shane@aptest.com> wrote:
> As to how it is done now.... there is a script that gets run to do an
> update.  But I don't know how it is triggered.  @davidlehn do you remember?
>

github has a hook with a secret token that makes a request to the site
to update itself.  I'm not sure exactly how the hook is setup since I
don't have github project admin rights.  Here's the code that gets
called:
https://github.com/perma-id/w3id.org/tree/master/.utils

Such hooks could run other code.  May need to consider other ways to
do the update if further processing is happening.  The git pull code
is atomic enough for now. But should consider how the site handles
redirs while the site is updating if there is an in-place processing
step.

-dave
Received on Monday, 29 February 2016 20:08:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:41 UTC