> On 22 Apr 2018, at 14:29, sebb <seb...@gmail.com> wrote: > > On 22 April 2018 at 13:04, Henk P. Penning <penn...@uu.nl > <mailto:penn...@uu.nl>> wrote: >> On Sun, 22 Apr 2018, sebb wrote: >> >>> Date: Sun, 22 Apr 2018 13:53:15 +0200 >>> From: sebb <seb...@gmail.com> >>> To: general@attic.apache.org >>> Subject: Re: svn commit: r1829770 - in /attic/site-json: build.props >>> build.sh >>> build.xml docs/projects/ lib/ xdocs/ >> >> >>>> Eh ; just a reminder ; the httpd config for www.a.o uses : >>>> >>>> RewriteCond "%%{}{REQUEST_URI}" "^/dist/([-a-zA-Z0-9]+)" >>>> RewriteCond "/var/www/attic.apache.org/projects/%1.html" -f >>>> RewriteRule ".*" "http://attic.apache.org/projects/%1.html"; [R=307,L] >>>> >>>> In other words : the /dist/GHOST/ redirects are triggered >>>> by the presence of "attic.apache.org/projects/GHOST.html". >>>> >>>> The point is that the lookup [-f] has to fast. >>>> In the future we should create a directory (like "flagged/") ; >>>> possibly combine the two, as in : >>>> >>>> attic.a.o/retired/ >>>> attic.a.o/retired/GHOST/ # retired flag >>>> attic.a.o/retired/GHOST/add-banner # banner flag >>> >>> >>> The dist redirect needs the plain host name, e.g. ace, whereas AFAIK >>> the banner processing needs FQDN, e.g. ace[.eu|us].apache.org. >>> So that won't work unless the banner processing can be changed to use >>> the plain host name. >> >> >> Right ; if we stay with /flagged/, the dist trigger can changed as : >> >> - RewriteCond "/var/www/attic.apache.org/projects/%1.html" -f >> + RewriteCond "/var/www/attic.apache.org/flagged/%1.apache.org/" -d >> >> ... and the banner-trigger : >> >> - <If "-d '/var/www/attic.apache.org/flagged/%%{}{HTTP_HOST}'"> >> + <If "-f '/var/www/attic.apache.org/flagged/%%{}{HTTP_HOST}/add-banner'"> > > Surely HTTP_HOST is GHOST.apache.org <http://ghost.apache.org/>? > For example we currently have: > > https://svn.apache.org/repos/asf/attic/site-json/docs/flagged/oltu.apache.org/oltu.apache.org > > <https://svn.apache.org/repos/asf/attic/site-json/docs/flagged/oltu.apache.org/oltu.apache.org> > >>> But I agree it would be good to reduce the number of files that have >>> to be created/amended for a new retirement. >> >> >> Eventually, we should generate the 'flagged' stuff. > > That would require a buildbot job or similar in order to make it > simpler for tablet users. > >>>> Does it make sense to have an (optional) 'dist' attribute, >>>> for sites where "lowercase(name)" is not equal to the >>>> the NAME in /dist/NAME ? >>> >>> >>> Which 'name' are you referring to here? >> >> >> The 'name' attribute in the JSON in "attic.js". > > I see. > That is the text for the project list in the RH menu, and is free-format. > It's not directly convertible into a dist/ directory name. > So I agree that a dist attribute would be needed for at least some entries. That is the reason for the “website” field. If we want to use the name alone, that field could be split in 2.
> > I hope dist names are the same as TLP website names but I've not checked. The field “board” was added where I had problems between the TLP name used in Whimsy and the normal name. In general adding fields to JSON should not be a problem. rgds Jan I. > >> Regards, >> >> >> HPP >> >> ------------------------------------------------------------ _ >> Henk P. Penning, ICT-beta R Uithof MG-403 _/ \_ >> Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \ >> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ >> http://www.staff.science.uu.nl/~penni101/ >> <http://www.staff.science.uu.nl/~penni101/> M penn...@uu.nl >> <mailto:penn...@uu.nl> \_/
